Restore a full backup from Settings
All checks were successful
Verify and publish V2 container / build-and-push (push) Successful in 30s
All checks were successful
Verify and publish V2 container / build-and-push (push) Successful in 30s
Settings → Data → Import gets "Restore a full backup" in place of the V1 import row. The zip from "Download backup" is uploaded and replaces the database, every setting and the uploaded files on the running server: - the staged database is upgraded to this schema (newer backups are refused), saved keys are re-encrypted for this server's key, interrupted jobs are marked, and the restoring session is carried over; - a pre-restore snapshot is written, running generations stop, and the file is swapped under the open DB handle (DB.replaceWith); uploads and media are copied into place and background work restarts. The /api/import/v1 endpoint stays for the V1 cutover (docs/MIGRATION.md). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
e0bc7b580e
commit
7125dec3e0
13 changed files with 521 additions and 72 deletions
|
|
@ -251,6 +251,12 @@ interface VectorCache {
|
|||
}
|
||||
let cache: VectorCache | null = null;
|
||||
|
||||
/** Drops the in-memory vectors (after a restore replaced the database). */
|
||||
export function resetVectorCache(): void {
|
||||
cache = null;
|
||||
queryCache.clear();
|
||||
}
|
||||
|
||||
function loadVectors(db: DB, key: string): VectorCache | null {
|
||||
const sig = db.get<{ n: number; m: number | null }>('SELECT COUNT(*) AS n, MAX(chunk_id) AS m FROM chunk_vectors WHERE model_key = ?', key)!;
|
||||
if (sig.n === 0) return null;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue