Deploy agnostic makes things much more difficult - you can't really rely on
git any more, unless you put something in to your own git commit / push
process that increments a file every commit.
What you're trying to determine is "has anything changed", not so much "what
git revision am I?"
This is kind of left field, but:
Once per app startup, "find app lib -type f -exec cat {} \; | md5sum"
Replace "app lib" with the directories that make up the changeable bits of
your app.
Will screw your startup time, obviously. Maybe you're approaching this
problem in the wrong way? Maybe generate a unique token on each app startup
(unicorn USR2, passenger tmp/restart.txt), have the user refresh if it's a
new token?
On Thu, Sep 1, 2011 at 10:04 AM, Malcolm Locke <[email protected]> wrote:
> On Thu, Sep 01, 2011 at 09:47:16AM +1000, Simon Russell wrote:
> > How are you deploying the app?
>
> That's one of the problems, it's an open source app, so could be
> deployed in a number of different ways. Would be ideal to have a deploy
> agnostic solution.
>
> 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.
>
>
--
Michael Pearson
The Bon Scotts; http://www.thebonscotts.com
--
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.
