ClusterCockpit/cc-backend
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-backend synced 2025-11-04 09:35:07 +01:00
Code Issues Packages Releases Activity

Update adm-upgrade.md

Browse Source
This commit is contained in:
Jan Eitzinger
2023-06-13 14:49:00 +02:00
committed by GitHub
parent 3766121aef
commit afadc30329
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/adm-upgrade.md
View File

@@ -16,13 +16,13 @@ in case the database needs to be migrated. In case of sqlite this means to stop
`cc-backend` and copy the sqlite databse file somewhere. `cc-backend` and copy the sqlite databse file somewhere.
# Migrating the database # Migrating the database
After backing up the database execute the the following command to migrate the After doing a database backup execute the following command to migrate the
databse to the most recent version: databse to the most recent version:
``` ```
$ ./cc-backend -migrate-db $ ./cc-backend -migrate-db
``` ```
The migration files are embedded into the binary but can be reviewed in the The migration files are embedded into the binary and can also be reviewed in the
cc-backend [source tree](https://github.com/ClusterCockpit/cc-backend/tree/master/internal/repository/migrations). cc-backend [source tree](https://github.com/ClusterCockpit/cc-backend/tree/master/internal/repository/migrations).
There are separate migration files for both supported database backends. There are separate migration files for both supported database backends.
We use the [migrate library](https://github.com/golang-migrate/migrate). We use the [migrate library](https://github.com/golang-migrate/migrate).