Skip to content

Dirman management dashboard

Current dashboard: https://assist.p3mdi.id. The notes below describe the original rollout.

Owner requested a quick management dashboard published at dirman.sumbu.xyz on the existing VPS. Build a separate FastAPI entrypoint in the existing image and a separate Compose service. Only this service joins the existing coolify proxy network; add host-specific Traefik HTTP-to-HTTPS and Let’s Encrypt labels. No existing proxy configuration changes or restarts. DNS is Cloudflare-owned; A record is currently absent and owner was asked to create it while work continues.

Scope: password login for an existing active administrator, secure HttpOnly session cookies, same-origin/CSRF write protection, login throttling, session expiry/logout/password change. No registration or anonymous management access. Secrets generated on server and delivered via protected server file, never embedded in frontend.

Views: overview; knowledge CRUD (FAQ/app/agenda/assignment/announcement, draft/published, optional expiry); ticket detail/status/assignment/notes; member search/role/active management with self/last-administrator protection. Store a small management audit trail. Existing private API and WhatsApp behavior remain compatible. Expired knowledge must not enter bot retrieval.

Visual brief: Indonesian, light warm paper #f6f3eb, white editing surface, deep blue-green #19343b navigation, teal #136f63 actions, slate #53656a body and rust #b45336 warning. Segoe UI/system sans for efficient reading. Left sidebar, broad table workspace and focused edit dialogs; no ornamental charts or invented metrics. Responsive navigation, keyboard-visible focus, native labels/dialogs, restrained motion. User-entered content uses textContent/value, never innerHTML.

Validation: authentication/CSRF/origin/revocation/throttle tests, member privilege boundaries, knowledge draft/expiry/update/delete, ticket assignment/notes; run existing isolated DB suite. Browser-check login, editing, ticket detail and mobile layout. Deploy privately first, provision credentials, add only this hostname’s routes, verify HTTPS certificate and anonymous API rejection when DNS is ready. If DNS remains unavailable, keep deployment complete and report the exact pending record.