build: autogenerate Coolify environment secrets
Use Coolify-generated database/JWT/admin secrets, assemble DATABASE_URL from the generated DB password, and document the single manual admin email plus rotation requirements.
This commit is contained in:
1 parent
e52e25e990
commit
dd2fc71867
4 files changed
+19
-26
No files matched your search
@@ -9,11 +9,11 @@ services:
|
||||
environment:
|
||||
NODE_ENV: production
|
||||
PORT: "3000"
|
||||
DATASTACK_JWT_SECRET: "${DATASTACK_JWT_SECRET:?Set DATASTACK_JWT_SECRET in .env}"
|
||||
DATASTACK_JWT_SECRET: "${SERVICE_REALBASE64_64_JWT:?Coolify must generate SERVICE_REALBASE64_64_JWT}"
|
||||
DATASTACK_ADMIN_EMAIL: "${DATASTACK_ADMIN_EMAIL:?Set DATASTACK_ADMIN_EMAIL in .env}"
|
||||
DATASTACK_ADMIN_PASSWORD: "${DATASTACK_ADMIN_PASSWORD:?Set DATASTACK_ADMIN_PASSWORD in .env}"
|
||||
DATASTACK_ADMIN_SESSION_SECRET: "${DATASTACK_ADMIN_SESSION_SECRET:?Set DATASTACK_ADMIN_SESSION_SECRET in .env}"
|
||||
DATABASE_URL: "${DATABASE_URL:?Set DATABASE_URL in .env}"
|
||||
DATASTACK_ADMIN_PASSWORD: "${SERVICE_PASSWORDWITHSYMBOLS_64_ADMIN:?Coolify must generate SERVICE_PASSWORDWITHSYMBOLS_64_ADMIN}"
|
||||
DATASTACK_ADMIN_SESSION_SECRET: "${SERVICE_REALBASE64_64_ADMINSESSION:?Coolify must generate SERVICE_REALBASE64_64_ADMINSESSION}"
|
||||
DATABASE_URL: "postgresql://datastack:${SERVICE_PASSWORD_64_POSTGRES:?Coolify must generate SERVICE_PASSWORD_64_POSTGRES}@postgres:5432/datastack_db"
|
||||
restart: unless-stopped
|
||||
healthcheck:
|
||||
test:
|
||||
@@ -40,7 +40,7 @@ services:
|
||||
environment:
|
||||
NODE_ENV: production
|
||||
PORT_SOCKET: "4000"
|
||||
DATASTACK_JWT_SECRET: "${DATASTACK_JWT_SECRET:?Set DATASTACK_JWT_SECRET in .env}"
|
||||
DATASTACK_JWT_SECRET: "${SERVICE_REALBASE64_64_JWT:?Coolify must generate SERVICE_REALBASE64_64_JWT}"
|
||||
restart: unless-stopped
|
||||
healthcheck:
|
||||
test:
|
||||
@@ -90,7 +90,7 @@ services:
|
||||
image: postgres:16-alpine
|
||||
environment:
|
||||
POSTGRES_USER: datastack
|
||||
POSTGRES_PASSWORD: "${POSTGRES_PASSWORD:?Set POSTGRES_PASSWORD in .env}"
|
||||
POSTGRES_PASSWORD: "${SERVICE_PASSWORD_64_POSTGRES:?Coolify must generate SERVICE_PASSWORD_64_POSTGRES}"
|
||||
POSTGRES_DB: datastack_db
|
||||
volumes:
|
||||
- pgdata:/var/lib/postgresql/data
|
||||
|
||||
+2
-1
@@ -14,7 +14,8 @@ Production container definitions for the split architecture:
|
||||
|
||||
- Create a Git-based Docker Compose application from branch `main`.
|
||||
- Set Base Directory to repository root `/` and Compose Location to `docker/docker-compose.yml`.
|
||||
- Set every required interpolated variable in Coolify: JWT/admin secrets and credentials, `DATABASE_URL`, and `POSTGRES_PASSWORD`.
|
||||
- Set `DATASTACK_ADMIN_EMAIL` in Coolify. The Compose definition uses Coolify-generated `SERVICE_PASSWORD_64_POSTGRES`, `SERVICE_REALBASE64_64_JWT`, `SERVICE_REALBASE64_64_ADMINSESSION`, and `SERVICE_PASSWORDWITHSYMBOLS_64_ADMIN`; it builds `DATABASE_URL` from the generated PostgreSQL password.
|
||||
- Retrieve the generated `SERVICE_PASSWORDWITHSYMBOLS_64_ADMIN` from Coolify Environment Variables for the initial admin sign-in. JWT/session/admin secrets can be rotated in Coolify. A PostgreSQL password change also requires updating the database role in the existing persistent volume; never paste secrets into Git-tracked files.
|
||||
- Add the public domain to service `proxy` at internal port `80`. Coolify manages proxy labels in its normal Compose mode; do not enable Raw Compose mode or add direct host port mappings.
|
||||
- The `web`, `ingestion`, Redis, and PostgreSQL services are private on the Compose network. Only the proxy is exposed to Coolify's domain proxy.
|
||||
- The `datastack-data` named volume persists ingestion CSVs; `pgdata` persists PostgreSQL files.
|
||||
|
||||
Reference in new issue
Block a user