From ecf1c7d4333a1d69e274a9eaa89fefe5dcf86b31 Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Thu, 7 Feb 2013 15:35:24 -0500 Subject: More blithering on autodeploy. --- wiki/devops/autodeploy.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) 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 -- cgit v1.2.3