Skip to content

Commit c7fb6b8

Browse files
committed
[exoframe-website] Update migration guide to mention pull before upgrade
1 parent 8e884a7 commit c7fb6b8

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • packages/exoframe-website/docs/migrating

packages/exoframe-website/docs/migrating/6-to-7.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar_position: 1
77
## TL;DR
88

99
- When upgrading to v7 - you will have to run `exoframe update` twice - first to update server to latest version, then to let server upgrade Traefik to v3 (Exoframe v6 only upgraded to latest v2).
10-
- The Exoframe server itself can be upgraded either with `exoframe upgrade` or by running the new `install.sh` script.
10+
- The Exoframe server itself can be upgraded either with `exoframe upgrade` or by running the new `install.sh` script (make sure to pull traefik and exoframe-server images before running the script).
1111
- Exoframe CLI now requires `deploy` subcommand to be explicitly passed. So, instead of `exoframe [-u] [folder]` you have to do `exoframe deploy [-u] [folder]`
1212
- Config for both Exoframe CLI and Exoframe Server is now located under `$XDG_CONFIG_HOME/exoframe` instead of `$HOME/.exoframe`
1313
- Server upgrade handles that automatically since it's a mount

0 commit comments

Comments
 (0)