[NX-203 Issue] Add production proxy profile with validation and documentation
All checks were successful
Container CVE Scan (development) / Scan backend/frontend images for CVEs (push) Successful in 2m40s
PostgreSQL Compatibility Matrix / PG14 smoke (push) Successful in 8s
PostgreSQL Compatibility Matrix / PG15 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG16 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG17 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG18 smoke (push) Successful in 8s
Proxy Profile Validation / validate (push) Successful in 3s
All checks were successful
Container CVE Scan (development) / Scan backend/frontend images for CVEs (push) Successful in 2m40s
PostgreSQL Compatibility Matrix / PG14 smoke (push) Successful in 8s
PostgreSQL Compatibility Matrix / PG15 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG16 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG17 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG18 smoke (push) Successful in 8s
Proxy Profile Validation / validate (push) Successful in 3s
Introduced a secure, repeatable production proxy profile for reverse proxy and HTTPS deployment, including NGINX configuration, environment variables, and CORS guidance. Added CI workflow for static validation of proxy guardrails and detailed documentation to ensure best practices in deployment.
This commit is contained in:
16
README.md
16
README.md
@@ -20,6 +20,7 @@ It combines FastAPI, React, and PostgreSQL in a Docker Compose stack with RBAC,
|
||||
- [API Error Format](#api-error-format)
|
||||
- [`pg_stat_statements` Requirement](#pg_stat_statements-requirement)
|
||||
- [Reverse Proxy / SSL Guidance](#reverse-proxy--ssl-guidance)
|
||||
- [Production Proxy Profile](#production-proxy-profile)
|
||||
- [PostgreSQL Compatibility Smoke Test](#postgresql-compatibility-smoke-test)
|
||||
- [Dependency Exception Flow](#dependency-exception-flow)
|
||||
- [Troubleshooting](#troubleshooting)
|
||||
@@ -372,6 +373,21 @@ For production, serve frontend and API under the same public origin via reverse
|
||||
|
||||
This prevents mixed-content and CORS issues.
|
||||
|
||||
## Production Proxy Profile
|
||||
|
||||
A secure, repeatable production profile is included:
|
||||
|
||||
- `ops/profiles/prod/.env.production.example`
|
||||
- `ops/profiles/prod/nginx/nexapg.conf`
|
||||
- `docs/deployment/proxy-production-profile.md`
|
||||
|
||||
Highlights:
|
||||
|
||||
- explicit CORS recommendations per environment (`dev`, `staging`, `prod`)
|
||||
- required reverse-proxy header forwarding for backend context
|
||||
- API path forwarding (`/api/` -> backend)
|
||||
- mixed-content prevention guidance for HTTPS deployments
|
||||
|
||||
## PostgreSQL Compatibility Smoke Test
|
||||
|
||||
Run manually against one DSN:
|
||||
|
||||
Reference in New Issue
Block a user