Maximilian Stubhan
b87c8ad64c
The database moved to a container of our own; the platform is gone. This takes out what was left of it — and, where the leftovers were load bearing, moves rather than deletes. Moved, not deleted: supabase/migrations/ -> db/migrations/ the schema's source of truth supabase/build-org.ts -> scripts/build-org.ts lib/supabase/types.ts -> lib/types.ts 52 import sites repointed The bookkeeping needed care. It lived in `supabase_migrations.schema_migrations`, and simply renaming the schema would have left the runner facing an empty table: it would have called all 67 migrations pending and replayed them against a database that is long since current. So the runner now creates `migrationen.schema_migrations` and, once, copies the old rows across — guarded so a second run does nothing and a fresh database skips it entirely. Only then does migration 20260907100000 drop the old schema. Deleted: the CLI config, the seed, the historical schema/function dumps (nothing read them), scripts/umzug-von-supabase.sh (the move is done), and both Supabase packages plus the CLI. Nothing in the application imported them — the build now succeeds with no environment variables at all, which is the proof. Integration tests: six of them signed in through Supabase Auth and asserted against the anon key and the service role. That model is gone, so the tests were not portable — they are deleted. session-context and employee-status-filter already ran on pg and are untouched; om-reporting is ported to a direct connection because it guards a real risk (the reporting line rule exists twice, once in SQL and once in TypeScript). CI: the integration job started a Supabase stack. It now runs a postgres service, applies deploy/db-init and every migration to an empty database — that was the valuable part, and it still holds — then checks that a second run is a no-op, which is what proves the bookkeeping works. Docs: security-review.md audited a service-role key, a cookie adapter and auth.users, none of which exist. Restating findings about removed components would suggest today's system had been reviewed; it has not. It now records what was removed and says a fresh review is due. data-model.md was already marked obsolete and described the pre-OM schema; azure-migration.md was a plan for a route not taken. Both deleted. Verified: npm ci, typecheck, lint, 445 tests, build — all clean without the packages. Integration tests skip cleanly with no database. Migration SQL and the runner are reviewed but NOT executed: no Docker here, and the old instance no longer resolves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
48 lines
1.9 KiB
TypeScript
48 lines
1.9 KiB
TypeScript
"use client";
|
|
|
|
import { AlertTriangle, RotateCcw } from "lucide-react";
|
|
import Link from "next/link";
|
|
import { useEffect } from "react";
|
|
import { Button, LINK_BUTTON_CLASS } from "@/components/ui/Button";
|
|
|
|
// Without this file a failed render drops the user on Next.js's own error
|
|
// screen — no navigation, no way back, and in production just "a client-side
|
|
// exception occurred". `reset()` re-renders the segment, which is enough for
|
|
// the common case of a transient database timeout.
|
|
export default function AppError({ error, reset }: { error: Error & { digest?: string }; reset: () => void }) {
|
|
useEffect(() => {
|
|
console.error("Route error:", error);
|
|
}, [error]);
|
|
|
|
return (
|
|
<div className="mx-auto flex max-w-lg flex-col items-start gap-4 rounded border border-border bg-white p-6">
|
|
<span className="flex h-10 w-10 items-center justify-center rounded-full bg-danger-bg text-danger-text">
|
|
<AlertTriangle className="h-5 w-5" />
|
|
</span>
|
|
<div>
|
|
<h1 className="text-lg font-bold text-ink">Diese Ansicht konnte nicht geladen werden</h1>
|
|
<p className="mt-1 text-sm text-ink-body">
|
|
Die Daten wurden nicht verändert. Meist hilft ein erneuter Versuch; bleibt der Fehler, wenden Sie sich bitte an die
|
|
IT-Betreuung.
|
|
</p>
|
|
</div>
|
|
{/* The digest is the only handle on the server-side stack trace, which
|
|
is deliberately not sent to the browser in production. */}
|
|
{error.digest && (
|
|
<p className="rounded bg-surface px-3 py-2 font-mono text-xs text-ink-muted">
|
|
Fehlerkennung: {error.digest}
|
|
</p>
|
|
)}
|
|
<div className="flex flex-wrap gap-2">
|
|
<Button onClick={reset}>
|
|
<RotateCcw className="h-4 w-4" />
|
|
Erneut versuchen
|
|
</Button>
|
|
<Link href="/" className={LINK_BUTTON_CLASS}>
|
|
Zur Übersicht
|
|
</Link>
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|