If you're using capistrano to deploy, Rails.root.basename.to_s will return the release dir name. That will be unique for each deploy.
The main problem here is that if you deploy the same code twice, the build id will change, which might be desirable, but probably isn't. On Thu, Sep 1, 2011 at 9:23 AM, malclocke <[email protected]> wrote: > I'm wondering if people have strategies for doing this. > > Background: I have a single page Javascript app backed by Rails. The > javascript is regularaly polling the server to check for updates on a > top level object's attributes, and triggering various events when > those attributes change. > > I'd like to add some kind of build identifier into the json that's > sent in response to the poll requests, so whenever a new deploy is > done I can trigger a 'There's an update, please reload the whole page' > pop-up. > > 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. > > Malc > > -- > 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. > > -- 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.
