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
Upfront: I don't think this is a high-priority feature, but I thought I'd write down the idea here to maybe get the ball rolling 🙂👟⚽️
When deploying with Capistrano, you usually get timestamped release directories for every deploy and the current, used one, is just a symlink to one of them:
This could be interesting for archival purposes as a first step so you have a trail of previously deployed releases to go back to. Later on it could allow for something like a mix bootleg.rollback <env> if desired. This would be useful to allow for quickly going back to a previous version if something's wrong with the last deployed release.
The revisions.log and repo will likely look differently (or not be available at all) as the build & app server are separate and in the end we only deploy a built release (which doesn't include a revision).
Like I wrote, not a high-prio feature right now, but maybe nice as a future extension to bootleg 👋
The text was updated successfully, but these errors were encountered:
Upfront: I don't think this is a high-priority feature, but I thought I'd write down the idea here to maybe get the ball rolling 🙂👟⚽️
When deploying with Capistrano, you usually get timestamped
release
directories for every deploy and thecurrent
, used one, is just a symlink to one of them:http://capistranorb.com/documentation/getting-started/structure/
This could be interesting for archival purposes as a first step so you have a trail of previously deployed releases to go back to. Later on it could allow for something like a
mix bootleg.rollback <env>
if desired. This would be useful to allow for quickly going back to a previous version if something's wrong with the last deployed release.The
revisions.log
andrepo
will likely look differently (or not be available at all) as the build & app server are separate and in the end we only deploy a built release (which doesn't include a revision).Like I wrote, not a high-prio feature right now, but maybe nice as a future extension to bootleg 👋
The text was updated successfully, but these errors were encountered: