Upgrade from 1.134 to 1.135.2 not allowing for custom DB name
I run two instances of Immich on Unraid 7.x (same box). One is my "prod" with pretty much default compose and env settings. The other is "staging" where I test things out. Since it's on the same box, I midified the compose and env to account for "-staging" in everything. For whatever reason when I created the staging, I named the DB "immich_staging" even though it's a dedicated instance of postgresql.
This has worked fine for months and over several upgrades. The upgrade to 1.135.2 though seems to have broken something. It appears from logs that the instance is looking for a database with the name of "immich" regardless of value in my env file. Almost like they hardcoded it and are ignoring the env.
Any tips on recovering this instance? Data is fine, I just can't bring up the server service.
Thanks for any help!
This has worked fine for months and over several upgrades. The upgrade to 1.135.2 though seems to have broken something. It appears from logs that the instance is looking for a database with the name of "immich" regardless of value in my env file. Almost like they hardcoded it and are ignoring the env.
Any tips on recovering this instance? Data is fine, I just can't bring up the server service.
Thanks for any help!
