forked from mtusi2026/mtusi2026lab5
Implement lab5 async image processing with RabbitMQ and outbox
This commit is contained in:
+18
-20
@@ -1,25 +1,23 @@
|
||||
# Copy to .env for your LOCAL synthetic test environment; never commit .env.
|
||||
# These are logical interface suggestions; map actual framework names in REPORT.md.
|
||||
APP_HOST=0.0.0.0
|
||||
APP_PORT=8080
|
||||
APP_ENV=lab
|
||||
# Copy to .env and REPLACE all sample secrets with random unique values.
|
||||
# For local synthetic data only. Never commit .env.
|
||||
POSTGRES_DB=messenger
|
||||
POSTGRES_USER=lab
|
||||
POSTGRES_PASSWORD=REPLACE_WITH_RANDOM_LOCAL_PASSWORD
|
||||
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
|
||||
S3_ENDPOINT=http://s3:9000
|
||||
S3_REGION=us-east-1
|
||||
DB_POOL_MAX=8
|
||||
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
|
||||
BROKER_URL_FILE=/run/secrets/broker_url
|
||||
WORKER_CONCURRENCY=2
|
||||
S3_ADMIN_ACCESS_KEY=adminlab4
|
||||
S3_ADMIN_SECRET_KEY=REPLACE_WITH_DIFFERENT_RANDOM_ADMIN_SECRET
|
||||
S3_ACCESS_KEY=messengerapi
|
||||
S3_SECRET_KEY=REPLACE_WITH_DIFFERENT_RANDOM_API_SECRET
|
||||
|
||||
# RabbitMQ persistent queue (different from session Redis).
|
||||
BROKER_USER=labworker
|
||||
BROKER_PASSWORD=REPLACE_WITH_RANDOM_LOCAL_BROKER_PASSWORD
|
||||
JOB_MAX_ATTEMPTS=5
|
||||
JOB_TIMEOUT_SECONDS=60
|
||||
STAGING_RETENTION_SECONDS=86400
|
||||
JOB_BACKLOG_LIMIT=1000
|
||||
WORKER_PREFETCH=1
|
||||
# Only for deliberate crash experiment: once. Keep off for normal operation.
|
||||
LAB5_FAULT_AFTER_S3=off
|
||||
|
||||
Reference in New Issue
Block a user