foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-20 17:26:56 -05:00
Code Issues Activity

Minor adjustments in the upgrade documentation (#915)

Browse source 
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/915
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: sandebert <sandebert@noreply.codeberg.org>
Co-committed-by: sandebert <sandebert@noreply.codeberg.org>
This commit is contained in:
sandebert 2024-11-07 10:20:40 +00:00 committed by Earl Warren
parent 96e7886a40
commit 028027fec6
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/admin/upgrade.md
View file

@ -50,12 +50,12 @@ It is **critical** to verify that Forgejo works very carefully. Restoring the ba
- Do not use `forgejo help` to figure out the location of `CustomPath`, look at the configuration tab of the `Site administration` panel when logged in as an admin.
- `forgejo manager flush-queues`. If it times out, run it again with a more generous `--timeout` argument. It is important because the queues contain serialized data that is not guaranteed to be backward compatible between versions.
Note: Forgejo requires [docker >= 20.10.6](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0) otherwise mysterious problems will happen (mysterious in the sense that the problem will about something unrelated to the Docker version").
Note: Forgejo installations using Docker requires [docker >= 20.10.6](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0) otherwise mysterious problems will happen (mysterious in the sense that the problem will about something unrelated to the Docker version").
## Performing the upgrade
- read the [list of things to know when upgrading from a specific version](#when-upgrading-from--known-problematic-versions-or-upgrade-paths) and either verify that your current version is not affected; or apply the notes appropriately
- otherwise, upgrade straight to the latest released Forgejo version (the upgrade procedure will take care of migrations)
- Read the [list of things to know when upgrading from a specific version](#when-upgrading-from--known-problematic-versions-or-upgrade-paths) and either verify that your current version is not affected; or apply the notes appropriately
- Otherwise, upgrade straight to the latest released Forgejo version (the upgrade procedure will take care of migrations)
- Verify Forgejo works
## Troubleshooting