Skip to content

Possible enhancement: Create timestamped deploy directories & symlink "current" #243

@pmeinhardt

Description

@pmeinhardt

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:

http://capistranorb.com/documentation/getting-started/structure/

├── current -> /var/www/my_app_name/releases/20150120114500/
├── releases
│   ├── 20150080072500
│   ├── 20150090083000
│   ├── 20150100093500
│   ├── 20150110104000
│   └── 20150120114500
├── repo
│   └── <VCS related data>
├── revisions.log
└── shared
    └── <linked_files and linked_dirs>

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 👋

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions