feat:v2 #12
11
.env.example
11
.env.example
@@ -9,3 +9,14 @@ DATABASE_PASSWORD=<password>
|
|||||||
DATABASE_NAME=calminer
|
DATABASE_NAME=calminer
|
||||||
# Optional: set a schema (comma-separated for multiple entries)
|
# Optional: set a schema (comma-separated for multiple entries)
|
||||||
# DATABASE_SCHEMA=public
|
# DATABASE_SCHEMA=public
|
||||||
|
|
||||||
|
# Default administrative credentials are provided at deployment time through environment variables
|
||||||
|
# (`CALMINER_SEED_ADMIN_EMAIL`, `CALMINER_SEED_ADMIN_USERNAME`, `CALMINER_SEED_ADMIN_PASSWORD`, `CALMINER_SEED_ADMIN_ROLES`).
|
||||||
|
# These values are consumed by a shared bootstrap helper on application startup, ensuring mandatory roles and the administrator account exist before any user interaction.
|
||||||
|
CALMINER_SEED_ADMIN_EMAIL=<email>
|
||||||
|
CALMINER_SEED_ADMIN_USERNAME=<username>
|
||||||
|
CALMINER_SEED_ADMIN_PASSWORD=<password>
|
||||||
|
CALMINER_SEED_ADMIN_ROLES=<roles>
|
||||||
|
# Operators can request a managed credential reset by setting `CALMINER_SEED_FORCE=true`.
|
||||||
|
# On the next startup the helper rotates the admin password and reapplies role assignments, so downstream environments must update stored secrets immediately after the reset.
|
||||||
|
# CALMINER_SEED_FORCE=false
|
||||||
Reference in New Issue
Block a user