immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2025-12-22 01:11:20 +03:00
Code Issues Packages Projects Releases 18 Wiki Activity

feat(server): env variable to skip migrations on startup (#9069)

Browse Source 
* env variable to skip migrations

* update docs

* update env doc
This commit is contained in:
Mert
2024-04-24 22:52:38 -04:00
committed by GitHub
parent f0f9053115
commit 466451abc9
6 changed files with 29 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/administration/backup-and-restore.md
View File

@@ -60,6 +60,10 @@ docker compose up -d # Start remainder of Immich apps
Note that for the database restore to proceed properly, it requires a completely fresh install (i.e. the Immich server has never run since creating the Docker containers). If the Immich app has run, Postgres conflicts may be encountered upon database restoration (relation already exists, violated foreign key constraints, multiple primary keys, etc.).
:::tip
Some deployment methods make it difficult to start the database without also starting the server or microservices. In these cases, you may set the environmental variable `DB_SKIP_MIGRATIONS=true` before starting the services. This will prevent the server from running migrations that interfere with the restore process. Note that both the server and microservices must have this variable set to prevent the migrations from running. Be sure to remove this variable and restart the services after the database is restored.
:::
The database dumps can also be automated (using [this image](https://github.com/prodrigestivill/docker-postgres-backup-local)) by editing the docker compose file to match the following:
```yaml