fix(db): reset the admin on Postgres and keep the key rotation off it

reset-admin.js opened data/travel.db with better-sqlite3 whatever the
engine, so on a Postgres install it created a stray SQLite file or reset
the admin in a leftover one. With TREK_DB_URL set it now resets the account
in Postgres through the built server's engine (its pool, SSL and write
lock, in one transaction), and refuses a TREK_DB_FILE beside the URL; the
SQLite branch is unchanged. migrate-encryption.ts cannot re-encrypt the
secrets in Postgres yet, so it now stops before it opens or writes any file
when TREK_DB_URL is set. The wiki says what each does on Postgres.
This commit is contained in:
Maurice
2026-11-17 12:16:12 +01:00
parent 7e8c74b8ff
commit 7a99190550
7 changed files with 257 additions and 83 deletions
+13
View File
@@ -141,6 +141,19 @@ async function main() {
console.log('This script re-encrypts all stored secrets under a new ENCRYPTION_KEY.');
console.log('A backup of the database will be created before any changes are made.\n');
// A Postgres install keeps its secrets in the database TREK_DB_URL names,
// which this script cannot rotate yet. It stops before it opens, creates or
// backs up any file: rotating a SQLite file left over from before the move
// would rewrite the key file while the secrets in Postgres stay under the
// old key.
if (process.env.TREK_DB_URL?.trim()) {
rl.close();
console.error('TREK_DB_URL is set: this install keeps its secrets in Postgres, which this script cannot');
console.error('re-encrypt yet. Nothing was changed. Keep the current ENCRYPTION_KEY; see the wiki page');
console.error('Encryption-Key-Rotation.');
process.exit(1);
}
// Resolve DB path
const dbPath = path.resolve(process.env.DB_PATH ?? path.join(__dirname, '../data/travel.db'));