diff options
| author | jrabbit <jackjrabbit@gmail.com> | 2022-12-06 17:24:04 +0000 |
|---|---|---|
| committer | jrabbit <jackjrabbit@gmail.com> | 2022-12-06 17:24:04 +0000 |
| commit | 8afad1e46ebdef3a4b4b74ea4d96121c6b3684a1 (patch) | |
| tree | e1c3aa22ed65ac25b8c1b1b3f1e4a94b955d9b73 | |
| parent | f60cb0f77145bf480c67e30ba8b356afda5834ab (diff) | |
| download | pleroma-8afad1e46ebdef3a4b4b74ea4d96121c6b3684a1.tar.gz pleroma-8afad1e46ebdef3a4b4b74ea4d96121c6b3684a1.zip | |
reccomend tagged releases over pulling stable
| -rw-r--r-- | docs/administration/updating.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/administration/updating.md b/docs/administration/updating.md index 01d3b9b0e..00eca36a0 100644 --- a/docs/administration/updating.md +++ b/docs/administration/updating.md @@ -17,7 +17,7 @@ su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate" ## For from source installations (using git) 1. Go to the working directory of Pleroma (default is `/opt/pleroma`) -2. Run `git pull` [^1]. This pulls the latest changes from upstream. +2. Run `git checkout <tagged release>` [^1]. e.g. `git checkout v2.4.5` This pulls the [tagged release](https://git.pleroma.social/pleroma/pleroma/-/releases) from upstream. 3. Run `mix deps.get` [^1]. This pulls in any new dependencies. 4. Stop the Pleroma service. 5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any. |