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
{{ message }}
This repository has been archived by the owner on Oct 16, 2018. It is now read-only.
Config vars should be versioned just like code releases. This probably means the env dir gets timestamped directories just like the release dir.
Timestamped env dirs with unchanged variables copied forward
A new app-level directory named versions
A "version" consists of a sequentially numbered directory in the versions directory, which then contains two symlinks. app points at the timestamped code release in releases, env points at the timestamped env in env. It also contains one real directory named procs, which is where pidfiles live (moved from the code release directory)
The current symlink points at the current version. The previous symlink can probably go away.
Add a set of version commands
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Config vars should be versioned just like code releases. This probably means the
env
dir gets timestamped directories just like therelease
dir.env
dirs with unchanged variables copied forwardversions
versions
directory, which then contains two symlinks.app
points at the timestamped code release inreleases
,env
points at the timestamped env inenv
. It also contains one real directory namedprocs
, which is where pidfiles live (moved from the code release directory)current
symlink points at the current version. Theprevious
symlink can probably go away.The text was updated successfully, but these errors were encountered: