diff options
| author | Owen Jacobson <owen.jacobson@grimoire.ca> | 2013-02-07 15:35:24 -0500 |
|---|---|---|
| committer | Owen Jacobson <owen.jacobson@grimoire.ca> | 2013-02-07 15:35:24 -0500 |
| commit | ecf1c7d4333a1d69e274a9eaa89fefe5dcf86b31 (patch) | |
| tree | 1ae3878bc3608359b68c301d1fcc709dc7157db9 | |
| parent | bcbd8fb90085d7328c6fdae5ed81b8a38e5e4785 (diff) | |
More blithering on autodeploy.
| -rw-r--r-- | wiki/devops/autodeploy.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/wiki/devops/autodeploy.md b/wiki/devops/autodeploy.md index ee05298..eff9ea6 100644 --- a/wiki/devops/autodeploy.md +++ b/wiki/devops/autodeploy.md @@ -23,3 +23,16 @@ wish on my worst enemy.) 5. For each service, in each environment, there is a canonical series of steps that produce a "deployed" system. + +----- + +1. Decide what code should be deployed. (This is a version control activity.) +2. Get the code onto the fucking server. +3. Decide what configuration values should be deployed. (This is also a + version control activity, though possibly not in the same repositories as + the code.) +4. Get the configuration onto the fucking server. +5. Get the code running with the configuration. +6. Log to fucking syslog. +7. When the machine reboots, make sure the code comes back running the same + configuration.
\ No newline at end of file |
