Comments on: Last deployment date with Rails and Capistrano

By: Frank

Frank — Mon, 28 Mar 2011 12:16:25 +0000

Josh, agreed. restart.txt is a bit less reliable than a custom dummy file for the reason you mention.

By: Josh Nesbitt

Josh Nesbitt — Mon, 28 Mar 2011 12:12:00 +0000

I’m not sure the last access time would suffice. What if you you needed to restart the application but haven’t deployed new code in-between restarts?

By: Frank

Frank — Mon, 28 Mar 2011 12:03:23 +0000

Bastian, that’’s a good idea! Even simpler for passenger users

By: Bastian Kruck

Bastian Kruck — Mon, 28 Mar 2011 01:37:24 +0000

When using passenger, why not check for the last change on tmp/restart.tmp?

File.atime(“#{Rails.root}/tmp/restart.txt”).strftime(“%Y-%m-%d at %H:%M”)

will work with just this single line :)

By: Last deployment date with Rails and Capistrano

Last deployment date with Rails and Capistrano — Fri, 10 Dec 2010 05:46:07 +0000

[...] while it is still in development. One thing I find useful is to display the last deployment… [full post] Frank Ruby Fleebie short & sweet 0 0 0 0 0 [...]

By: Frank

Frank — Fri, 19 Mar 2010 17:26:05 +0000

Thanks guys for these nice alternatives!

By: Josh Nesbitt

Josh Nesbitt — Fri, 19 Mar 2010 16:29:31 +0000

You could also pull the timestamp from the most recent folder within the releases directory, as Capistrano uses timestamped folder names as a way of separating revisions of code over different deploys. Nice idea :)

By: Ian Neubert

Ian Neubert — Fri, 19 Mar 2010 15:49:56 +0000

I think you could also use the REVISION file that capistrano places by default during a deploy. You could also get the SVN/git revision from this file by reading it.

Thanks for the tip!