A Git commit is not deployment proof. Installed host Compose version is not
proof of Portainer's Compose implementation.
Recovering deployment requires Portainer state or independently retrievable
repository credentials and stack environment values. Portainer backups
exist; credential/state restoration is untested. Do not put secret values in
this site or Git.
No independent recovery arrangement exists for the PAT or stack secrets.
Rollback, health-check gates, approval rules and UI-versus-Git drift policy
are not established; do not assume permission to deploy, stop or delete services.
Authentik configuration surfaces
The owner reports the Authelia-to-Authentik migration complete. Rebuilding it
requires more than pulling Compose:
Copy repository stacks/authentik/blueprints/jupiter.yaml into /data/authentik/blueprints; Git checkout alone does not populate this bind mount
Authentik database
Administrator, MFA enrolment, group memberships, applied providers/application policies
Application databases/UIs
Beszel, Gitea, Immich and Portainer OIDC setup/account linking
Application Compose
Dozzle, Paperless and Wardrowbe OIDC settings; five proxy-protected routers use authentik@docker
For initial setup, keep AUTHENTIK_PUBLIC_ROUTING=false and access the
loopback-published 127.0.0.1:9000 privately, for example through SSH forwarding.
Secure the administrator account and prepare MFA, groups and blueprint policy
before enabling public routing. Enable routing and establish working OIDC
account links before disabling any local application login; Beszel/Paperless
flags default to preserving it. The retired Authelia service is not a
replacement recovery path.
Redeploying the Authentik stack alone does not copy changed host blueprints
or reproduce database-backed application settings. Keep provider/client secrets
matched across both sides. Preserve deployed Authentik container names or update
the Backrest hooks when recreating containers.
Host apt packages, fstab, RAID assembly, systemd units and Mercury nginx are
outside the Compose deployment workflow.