4 Commits

Include renames

Author	SHA1	Message	Date
Stefan Lazic	ba46334179	Delete Business ... A Delete button now sits next to Edit on each business's detail page, styled in red to distinguish it from the safe actions. It opens a dedicated confirmation page (matching the Add/Edit page pattern) that clearly lists exactly what gets destroyed — container + media volume, the database by name, the Caddy site/domain, and the stack directory — and requires typing the business's exact slug before the Delete button even becomes clickable. This is a stronger guard than a plain "are you sure?" popup, given what we just learned about how easy it is to lose data here. deleteBusiness() in provisioning.ts reuses the same primitives as create/edit (composeDown, reloadCaddy, the shared MySQL root connection), and is deliberately best-effort past the first step — if a piece is already gone (matching exactly the kind of half-broken state we just fixed for blake-heritage), it still finishes removing the rest and reports what it couldn't clean up automatically, rather than getting stuck. Verified live: provisioned a real test business, confirmed its container/database/user/volume/Caddy site all existed, deleted it, and confirmed every single one was actually gone — including checking Caddy's running config (not just the file on disk) to prove the reload took effect. Also confirmed the confirm-button correctly stays disabled for a wrong slug and only enables on an exact match. Your real production database was never touched throughout.	2026-09-05 17:41:38 +01:00
Stefan Lazic	2e739c9a26	Update provisioning.ts	2026-09-05 17:14:39 +01:00
Stefan Lazic	3b07124d7e	Edit Business flow ... New files: manager/src/lib/env-file.ts — a shared, surgical .env reader/updater. It only ever touches the specific keys you tell it to (never regenerates the file), so anything hand-edited into a business's .env since provisioning is preserved exactly. manager/src/app/dashboard/[slug]/edit/ — the edit page, its form component, and its server action. Modified: provisioning.ts gained updateBusiness() alongside the existing provisionBusiness(), reusing the same Caddy-site-writing and container-recreation logic (refactored into a shared writeCaddySiteAndReload helper). stacks.ts/compose-template.ts — extended to track a BUSINESS_NAME field (previously collected on the Add Business form but silently discarded — that gap is now fixed too, so newly created businesses get their name persisted from the start). The detail page and dashboard list now show the business name, and the detail page has an Edit button. Per the requirements: Slug is read-only in the edit form (disabled input, never accepted by the server action — it's bound in from the route, not form data). Domain uniqueness is validated against every other business (and correctly self-excludes the business being edited). A domain change rewrites the Caddy site file, reloads Caddy, and force-recreates the container; a name-only change does neither. No secrets (DATABASE_PASSWORD, AUTH_SECRET, etc.) are ever read into the edit UI — only name/domain/databaseName/status are exposed. Clear success banners ("Changes saved" vs. "...the container was restarted...") and inline error display, matching the existing Add Business pattern.	2026-09-05 17:05:33 +01:00
Stefan Lazic	a0d39026c0	Management UI ... Attempt 2 of a management ui.	2026-09-05 13:39:55 +01:00