fragginwagon
c728016dec
Includes MFA-capable authentication, session and CSRF security, password recovery, listing lifecycle and ownership rules, inventory image metadata, local ImageStorage, migrations, tests, and implementation status documentation. Verification: npm test (62 passing) and integration suite (14 passing).
59 lines
1.1 KiB
Markdown
59 lines
1.1 KiB
Markdown
# Deployment
|
|
|
|
## Environments
|
|
|
|
- development
|
|
- test/CI
|
|
- production
|
|
|
|
## Docker Compose
|
|
|
|
Baseline services:
|
|
- frontend
|
|
- API
|
|
- worker
|
|
- PostgreSQL
|
|
- Redis
|
|
- reverse proxy
|
|
|
|
Persistent data:
|
|
- PostgreSQL data
|
|
- Redis data where needed
|
|
- image storage
|
|
|
|
## Reverse proxy
|
|
|
|
Responsible for:
|
|
- HTTPS/TLS
|
|
- routing
|
|
- compression
|
|
- security headers
|
|
- rate limiting where appropriate
|
|
|
|
## Configuration
|
|
|
|
Environment variables/secrets:
|
|
- database connection
|
|
- Redis connection
|
|
- authentication/session secrets
|
|
- provider credentials
|
|
- email credentials
|
|
- storage credentials
|
|
|
|
Application settings such as pricing strategy and site settings belong in the database.
|
|
|
|
## Backups
|
|
|
|
Back up:
|
|
- PostgreSQL
|
|
- image storage
|
|
- required environment/configuration information
|
|
|
|
Retention policy and restore procedures must be documented for production.
|
|
|
|
Disaster recovery should allow reconstruction elsewhere from database backup, image backup, and deployment/environment configuration.
|
|
|
|
## Future hosting
|
|
|
|
Initial deployment targets a home server/NAS. The architecture should allow later movement to an online server or managed infrastructure without redesigning the domain model.
|