Config belongs in the database (fixed convention); the stack carries only what
the app needs to start. Onboarding is no longer wired through the compose.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove the onboarding vars from the committed .env. The compose still passes
them through as ${VAR:-} (optional), so onboarding stays configurable via
Portainer without cluttering .env or warning on deploy.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Revert the over-hardcoding: Postgres connection settings (host/port/db/user/
password) and TZ are env vars again. The only value fixed in the compose is the
Postgres image version (functional dependency). No silent defaults remain
(${VAR:?}); POSTGRES_PASSWORD ships empty and must be set in Portainer.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove silent defaults (every per-deploy value via ${VAR:?}), hardcode the
fixed structural constants in compose, and key container names + the Postgres
data dir off CLEARVIEW_ENV (dev/prod) so dev and prod stacks coexist. Image tag
stays CLEARVIEW_IMAGE_TAG (dev/latest).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Full application including FastAPI backend, PostgreSQL data model,
background scan worker, multi-tenant support, certificate authentication,
SharePoint REST scanner with hierarchical deduplication, SharingLinks
classification and post-scan resolve, Excel export, site filter in job
details, role name normalisation, and updated documentation.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
