feat(infra): create staging docker-compose and environment configuration #67
Reference in New Issue
Block a user
Delete Branch "infra/stage-deploy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This pull request introduces a production-grade, security-hardened Docker Staging environment configuration for NexusReader, prepared directly from the
developbranch.🚀 Key Additions
docker-compose.stage.yml:nexus-web-stage,nexus-db-stage,nexus-qdrant-stage,nexus-neo4j-stage) inside a dedicatednexus-stagebridge network.5080, Postgres on5438, Neo4j HTTP on7488).curlfor Qdrant,wgetfor Neo4j,pg_isreadyfor Postgres).pgdata_stage,qdrant_stage_data,neo4j_stage_data) to prevent data loss.stage_www_uploadsfor EPUBs,stage_www_coversfor covers) without overriding the compiled static web client files..env.stage.template:.env.stagelocally during deployment to inject secrets securely.NEXUS_ADMIN_PASSWORD(checked byDbInitializerfor staging/production builds)..gitignore:.env.stage) to prevent accidentally committing credentials, while keeping the.env.stage.templatetracked.🧪 Verification Performed
docker compose -f docker-compose.stage.yml --env-file .env.stage configsuccessfully with zero configuration or parsing errors.dotnet build NexusReader.slnx --no-restorefrom root — SUCCESS with0compile errors.dotnet test --no-restore— SUCCESS (all 20/20 unit tests passed).