diff options
| author | elijah <elijah@riseup.net> | 2016-09-14 15:24:14 -0700 |
|---|---|---|
| committer | elijah <elijah@riseup.net> | 2016-09-14 15:24:14 -0700 |
| commit | c7d1deadf7cf21a619105252145e0bea3e9e3f58 (patch) | |
| tree | 64904d7fdf13e4a8e32eb391c939809c8746be60 | |
| parent | 996b796992f2839a4f73083f2b9364cd41b3c7a4 (diff) | |
added 0.9 upgrade guide
| -rw-r--r-- | docs/platform/amber/menu.txt | 1 | ||||
| -rw-r--r-- | pages/docs/platform/upgrading/upgrade-0-9.md | 45 |
2 files changed, 46 insertions, 0 deletions
diff --git a/docs/platform/amber/menu.txt b/docs/platform/amber/menu.txt index 819600a..88453a6 100644 --- a/docs/platform/amber/menu.txt +++ b/docs/platform/amber/menu.txt @@ -23,6 +23,7 @@ services tor webapp upgrading + upgrade-0-9 upgrade-0-8 troubleshooting tests diff --git a/pages/docs/platform/upgrading/upgrade-0-9.md b/pages/docs/platform/upgrading/upgrade-0-9.md new file mode 100644 index 0000000..f2b8390 --- /dev/null +++ b/pages/docs/platform/upgrading/upgrade-0-9.md @@ -0,0 +1,45 @@ +@title = 'Upgrade to 0.9' +@toc = false + + +Upgrading to Platform 0.9 +--------------------------------------------- + +You will need the new version of leap_cli: + + workstation$ sudo gem install leap_cli --version=1.9 + +If you don't want to install using 'sudo': + + workstation$ gem install --user-install leap_cli --version=1.9 + workstation$ PATH="$PATH:$(ruby -e 'puts Gem.user_dir')/bin" + +Because 0.9 does not use submodules anymore, you must remove them before pulling +the latest leap_platform from git: + + workstation$ cd leap_platform + workstation$ for dir in $(git submodule | awk '{print $2}'); do + workstation$ git submodule deinit $dir + workstation$ done + workstation$ git pull + workstation$ git checkout 0.9.0 + +Alternately, just clone a fresh leap_platform: + + workstation$ git clone https://leap.se/git/leap_platform + workstation$ cd leap_platform + workstation$ git checkout 0.9.0 + +Then, just deploy + + workstation$ cd PROVIDER_DIR + workstation$ leap deploy + +Known issues +--------------------------------------------- + +When upgrading, sometimes systemd does not report the correct state of a daemon. +The daemon will be not running, but systemd thinks it is. The symptom of this is +that a deploy will succeed but `leap test` will fail. To fix, you can run +`systemctl stop DAEMON` and then `systemctl start DAEMON` on the affected host +(systemctl restart seems to work less reliably).
\ No newline at end of file |