I second the question.
FWIW the current deploy procedure I use for $job (written by a colleague) is an unholy mix of jammit, spritemapper, rake, %x{git} and asset_id.
It _does_ work, but I am quite looking forward to the integration of rails 3.1 to get rid of it.
Comments
I second the question. FWIW the current deploy procedure I use for $job (written by a colleague) is an unholy mix of jammit, spritemapper, rake, %x{git} and asset_id.
It _does_ work, but I am quite looking forward to the integration of rails 3.1 to get rid of it.