diff options
| author | varac <varacanero@zeromail.org> | 2013-11-12 16:27:52 +0100 |
|---|---|---|
| committer | varac <varacanero@zeromail.org> | 2013-11-12 16:27:52 +0100 |
| commit | 3b74801d0ccc9a08b8404f9792114c346f780e26 (patch) | |
| tree | 9da664648b8c339250173b08b1c5f5deeb743b4c | |
| parent | 8a2196d78ffce27374f0ef400c1554d1fcc9230e (diff) | |
document need to deploy couch node before webapp node (Feature #3768)
| -rw-r--r-- | docs/platform/quick-start.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/platform/quick-start.md b/docs/platform/quick-start.md index 2987466..3b5f33c 100644 --- a/docs/platform/quick-start.md +++ b/docs/platform/quick-start.md @@ -283,15 +283,16 @@ If you prefer, you can initalize each node, one at a time: Deploy the LEAP platform to the nodes -------------------- -Now you should deploy the platform recipes to the nodes. Deployment can take a while to run, especially on the first run, as it needs to update the packages on the new machine: +Now you should deploy the platform recipes to the nodes. Deployment can take a while to run, especially on the first run, as it needs to update the packages on the new machine. +Note that currently, nodes must be deployed in a certain order. The underlying couch database node(s) must be deployed first, and then all other nodes. - $ leap deploy web1 + $ leap deploy couch1 Watch the output for any errors (in red), if everything worked fine, you should now have your first running node. If you do have errors, try doing the deploy again. However, to deploy our three-node openvpn setup, we need the database and LEAP web application requires a database to run, so let's deploy to the couchdb and openvpn nodes: - $ leap deploy couch1 + $ leap deploy web1 $ leap deploy vpn1 NOTE: the output from deploying can be quite busy, so we often do them each node one by one. |