Files
Brandon LiandClaude Fable 5 8154f25bb9 Backups to master, replacement-VPS restore, broker proxy, multi-instance
Four features:

- Backup: lib/backup-sync.ts pushes the full settings table and firm
  credentials (the deliberate exception to "credentials never leave the
  machine") to the master's bearer-gated /api/instances/backup — every
  5 minutes when the content hash changed, within seconds of a settings
  or credential edit, and on the new backup-now command. Enabled by the
  master_backup_token setting.

- Restore: a dead VPS's replacement pulls the backup and adopts its
  uuid/name, so roster, payouts and card links carry on. Pre-boot via
  seed-settings.js --restore-from (setup-linux.sh prompts for it) or
  the Settings page's restore picker (lib/backup-restore.ts). Stop the
  old machine first; the master 409s a live-name rename.

- Proxy: the proxy_url setting routes BROKER traffic only — TopstepX
  REST + SignalR hub, Tradovate REST + websocket, Yahoo quotes — via
  lib/outbound-proxy.ts (axios agents, undici dispatcher, ws agent).
  The master link, reporter, catalog and backup push stay direct, so a
  dead proxy cannot take down the control channel. Restart to apply.

- Multi-instance: AUTOFIRMER_DB moves the SQLite file so one checkout
  runs N instances; scripts/instances.json (per-device, gitignored)
  drives start-all/update-check, and add-instance.sh / remove-instance.sh
  manage the extra PM2 processes. Absent registry = single-instance
  behavior, unchanged. Instance 1 keeps port 3000 for the clicker and
  extension.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-22 13:55:35 -05:00

69 lines
2.6 KiB
TypeScript

import { NextRequest, NextResponse } from 'next/server';
import { getSetting } from '@/lib/db';
import { applyBackup, fetchBackup, fetchBackupList } from '@/lib/backup-restore';
/**
* Restore-from-master for the settings page.
*
* The browser talks to this route and this route talks to the master with the
* machine's own stored master_dashboard_url + master_backup_token, so the
* token never reaches the browser.
*
* GET — the available backups, for the picker.
* POST { id } — pull that backup and apply it, adopting its identity.
* The process must be restarted afterwards; the response says so.
*/
function config(): { masterUrl: string; token: string } | NextResponse {
const masterUrl = getSetting('master_dashboard_url');
const token = getSetting('master_backup_token');
if (!masterUrl) return NextResponse.json({ error: 'master_dashboard_url is not set' }, { status: 400 });
if (!token) return NextResponse.json({ error: 'master_backup_token is not set' }, { status: 400 });
return { masterUrl, token };
}
export async function GET() {
const cfg = config();
if (cfg instanceof NextResponse) return cfg;
try {
const backups = await fetchBackupList(cfg.masterUrl, cfg.token);
return NextResponse.json({ backups });
} catch (err) {
const error = err instanceof Error ? err.message : String(err);
return NextResponse.json({ error }, { status: 502 });
}
}
export async function POST(req: NextRequest) {
const cfg = config();
if (cfg instanceof NextResponse) return cfg;
let id = '';
try {
const body = await req.json();
id = typeof body?.id === 'string' ? body.id.trim() : '';
} catch { /* falls through to the check below */ }
if (!id) return NextResponse.json({ error: 'id is required' }, { status: 400 });
try {
const payload = await fetchBackup(cfg.masterUrl, cfg.token, id);
const restored = applyBackup(payload);
return NextResponse.json({
ok: true,
restored,
savedAt: payload.savedAt,
adopted: {
name: payload.settings.instance_name ?? '',
id: payload.settings.instance_id ?? '',
},
// Live platform clients, the master link's hello and the proxy all
// predate the restore — a restart is the only honest way in.
restartRequired: true,
});
} catch (err) {
const error = err instanceof Error ? err.message : String(err);
return NextResponse.json({ error }, { status: 502 });
}
}