github/TREK
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: point upgraders to ./data/.jwt_secret in ENCRYPTION_KEY error and docs

Browse Source 
The startup error now tells operators exactly where to find the old key
value (./data/.jwt_secret) rather than just saying "your old JWT_SECRET".
docker-compose.yml and README updated to mark ENCRYPTION_KEY as required
and remove the stale "auto-generated" comments.
This commit is contained in:
jubnl
2026-04-01 08:43:10 +02:00
parent 358afd2428
commit 19350fbc3e
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
server/src/config.ts
View File

@@ -48,8 +48,8 @@ const ENCRYPTION_KEY: string = process.env.ENCRYPTION_KEY || '';
if (!ENCRYPTION_KEY) {
console.error('FATAL: ENCRYPTION_KEY is not set.');
console.error('If this occurs after an update from a version that derived encryption from JWT_SECRET,');
console.error('set ENCRYPTION_KEY to the value of your old JWT_SECRET to keep existing secrets readable.');
console.error('If this occurs after an update, set ENCRYPTION_KEY to the value of your old JWT secret.');
console.error('Your JWT secret is stored in data/.jwt_secret (host path: ./data/.jwt_secret).');
console.error('For a fresh install, generate a random key: openssl rand -hex 32');
process.exit(1);
}