Files
mtusi2026lab4/.env.example
T

45 lines
1.5 KiB
Bash

# Copy to .env for your LOCAL synthetic test environment; never commit .env.
# These are logical interface suggestions; map actual framework names in REPORT.md.
# Host process (make run); the container binds 0.0.0.0 in Dockerfile.
APP_HOST=127.0.0.1
APP_PORT=8080
APP_ENV=lab
SESSION_TTL_SECONDS=3600
# Choose credentials locally. File paths contain no secret values.
DATABASE_URL_FILE=/run/secrets/database_url
# Optional on 3, required use on 4 in lab2; Redis OR Valkey:
SESSION_STORE=postgres
CACHE_URL_FILE=/run/secrets/cache_url
API_REPLICAS=2
IDEMPOTENCY_TTL_SECONDS=86400
# Lab 4 logical names (skeleton). Containers get S3_ENDPOINT from compose.yaml,
# make run overrides it with 127.0.0.1:S3_HOST_PORT; keys come from the lines below.
S3_ENDPOINT=http://s3:9000
S3_REGION=us-east-1
S3_BUCKET=messenger-attachments
S3_ACCESS_KEY_ID_FILE=/run/secrets/s3_access_key_id
S3_SECRET_ACCESS_KEY_FILE=/run/secrets/s3_secret_access_key
MAX_UPLOAD_BYTES=10485760
MAX_IMAGE_PIXELS=40000000
# Compose and make run. make env fills the empty passwords and keys locally.
HOST_PORT=8080
POSTGRES_USER=messenger
POSTGRES_DB=messenger
POSTGRES_PASSWORD=
POSTGRES_HOST_PORT=5433
VALKEY_PASSWORD=
VALKEY_HOST_PORT=6380
LOG_LEVEL=INFO
SHUTDOWN_TIMEOUT=5
# S3 (SeaweedFS): the root pair and the signing key stay with the s3 server;
# the API and the cleaner have their own users created by s3-bootstrap.
S3_HOST_PORT=8334
S3_ROOT_ACCESS_KEY=
S3_ROOT_SECRET_KEY=
S3_JWT_SIGNING_KEY=
S3_API_ACCESS_KEY=
S3_API_SECRET_KEY=
S3_CLEANER_ACCESS_KEY=
S3_CLEANER_SECRET_KEY=