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

"loose" should be "lose"

Browse source 
# Conflicts:
#	v1.19/admin/upgrade.md
This commit is contained in:
Cyborus 2023-07-26 15:35:53 -04:00 committed by Caesar Schinas
parent 10f14eff87
commit 8ad4341dd6
No known key found for this signature in database
GPG key ID: AE9108461BEA5ACF
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
admin/upgrade.md
View file

@ -24,7 +24,7 @@ In the simplest case where everything is on a single file system and if the inst
### Verify Forgejo works
It is **critical** to verify that Forgejo works very carefully. Restoring the backup done before the upgrade is easy and does not loose any information. But if a problem is discovered days or weeks after the upgrade, it will not be an option and fixing it on a live Forgejo instance will be much more challenging.
It is **critical** to verify that Forgejo works very carefully. Restoring the backup done before the upgrade is easy and does not lose any information. But if a problem is discovered days or weeks after the upgrade, it will not be an option and fixing it on a live Forgejo instance will be much more challenging.
- Run `forgejo doctor --all --log-file /tmp/doctor.log` and make sure it does not report any problem.
- Manually verify via the web interface. Making a checklist of a typical use case is a good way to not miss anything.