Perhaps you could take the 3.1 approach of an MD5. Have a rake task that during deploy concats all your models, controllers and anything else relevant then takes an md5 of that and uses that as your "build id". Although I think it would be ideal if it was completely transparent (i.e. you didn't need to know to run it at deploy time).
- Ben On Thursday, 1 September 2011 at 9:49 AM, James Healy wrote: > On 1 September 2011 09:23, malclocke <[email protected] > (mailto:[email protected])> wrote: > > I guess ideally I'd like to include the git commit id in code somehow, > > but svn style keyword substitution seems to be discouraged. I'd like > > the solution to work if the deployed code is not actually a git > > checkout. I'd like a solution that doesn't require me to manually > > update a config version number somewhere. > > I create a git tag to mark each deploy and allow easy diffs between > deploys, etc. > > During each deploy, I run "git describe --abbrev=0 > db/tag.txt" to > output the current tag to a file. That's then used in the code when I > want to check the release/build version. > > James > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
