From 4351ea2d6ec11e0f9a460d43425eddb5af7f4748 Mon Sep 17 00:00:00 2001 From: Lance Edgar Date: Sat, 15 Feb 2025 21:34:28 -0600 Subject: [PATCH] Add Deployment-BootstrapServer --- Deployment-BootstrapServer.-.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Deployment-BootstrapServer.-.md diff --git a/Deployment-BootstrapServer.-.md b/Deployment-BootstrapServer.-.md new file mode 100644 index 0000000..8d11bfc --- /dev/null +++ b/Deployment-BootstrapServer.-.md @@ -0,0 +1,22 @@ +# Bootstrap a Server + +This page describes the steps to actually "bootstrap" (install/configure) a target server. + +This assumes the following as prerequisites: + + * You should already have set up your local [control environment](Deployment-ControlEnvironment.-). + * You should already have a local copy of your source repository. (Or you can use the [demo project](Deployment-Demo.-).) + * You should already have [prepared the server bundle](Deployment-ServerBundlePrep.-). + * You should already have [prepared the target machine](Deployment-ServerMachinePrep.-). + +## Install and Configure Software + +Performing the actual install of software etc. is done using Fabric. Assuming a typical server bundle, there should be a `bootstrap_all` task which is capable of installing and configuring everything in order to make the server fully operational. Assuming your current working directory is the root of a server bundle then, the command would look like: + +```sh +fab bootstrap_all +``` + +That's it, as far as the minimum goes. In practice you may of course need to provide additional arguments to the `fab` command, depending on your setup. + +Note that this `bootstrap_all` command is meant to perform initial install ''and'' later upgrade. It should be written such that you can run it as many times as you like, and the end result should always be the same: a fully operational server.