Parker Selbert wrote: [...] > Really the idea was that you would remove writing markup as part of your > deploy recipe,
I agree with this too. If your deploy recipe is writing markup, something is very, very wrong. If you just set a constant VERSION with your deploy recipe, then you won't have your deploy recipe reaching so far into your app code. In other words: a properly written deploy recipe can set configuration values, but should not otherwise change your app. That implies that it can touch initializers and config files, but should not touch anything in Rails.root/app . Otherwise, you're setting yourself up for weird maintenance problems, I think. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
