You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Important: GitHub issues are for feature requests or bug reports. The Capistrano team recommends you use Stack Overflow for general questions. For more details, please see our contribution policy.
A while ago we had a request from a client that we have a light-weight "versioning" field in the admin panel of their app so they could check if there had been a new deployment - since we use continuous integration and deploy to autoblanced servers we couldn't use the release time as that is effectively arbitrary and not consistent (e.g. if we don't deploy for two weeks and a server is reprovisioned, it'll have a very different release time to the other servers), so to facilitate this we implemented a REVISION_TIME file into our Capistrano deployment which works pretty much exactly how the existing REVISION file does, just with Time™.
We saw this as useful to have in general so landed it in our rails-template (ackama/rails-template#461) and have ported it to a number of our apps without issue.
This is something that feels like a useful and cheap win to be worth having upstreamed into Capistrano itself, especially since most of the code in that PR is just copied from what already exists in Capistrano since (afaik) there's no way to hook in any "closer".
The text was updated successfully, but these errors were encountered:
Important: GitHub issues are for feature requests or bug reports. The Capistrano team recommends you use Stack Overflow for general questions. For more details, please see our contribution policy.
A while ago we had a request from a client that we have a light-weight "versioning" field in the admin panel of their app so they could check if there had been a new deployment - since we use continuous integration and deploy to autoblanced servers we couldn't use the release time as that is effectively arbitrary and not consistent (e.g. if we don't deploy for two weeks and a server is reprovisioned, it'll have a very different release time to the other servers), so to facilitate this we implemented a
REVISION_TIME
file into our Capistrano deployment which works pretty much exactly how the existingREVISION
file does, just with Time™.We saw this as useful to have in general so landed it in our
rails-template
(ackama/rails-template#461) and have ported it to a number of our apps without issue.This is something that feels like a useful and cheap win to be worth having upstreamed into Capistrano itself, especially since most of the code in that PR is just copied from what already exists in Capistrano since (afaik) there's no way to hook in any "closer".
The text was updated successfully, but these errors were encountered: