Security & backups

Trust and privilege

Portal runs unprivileged; a root-owned helper validates fixed host operations. Secure production cookies, session checks, CSRF and organization grants protect dashboard access. Repository code is still trusted executable code. Compose restrictions and organization permissions do not provide hostile-tenant isolation.

Back up the matching set

• Keep /etc/dashboard-portal/dashboard-portal.env with /var/lib/dashboard-portal, including the original encryption key.
• Use a consistent SQLite backup or pause writers during a planned snapshot. Copying only a live .sqlite file can omit WAL changes.
• Back up project releases/environments, Docker volumes, external databases, Nginx and /etc/letsencrypt as required by your application.
• Encrypt and restrict backup access. Installer snapshots are not full host backups.

Prove restoration

Restore onto staging using the original key, correct ownership and permissions. Verify login, organizations, projects, readable encrypted values and application data. Test a deployment and rollback before relying on the backup. An old application binary is not a substitute for an access-model migration recovery plan.