feat: Add Docker support and CI/CD workflows documentation; include setup instructions for Docker-based deployment

docs/architecture/07_deployment_view.md

@@ -4,6 +4,8 @@ description: "Describe deployment topology, infrastructure components, and envir
 status: draft
 ---
 
+<!-- markdownlint-disable-next-line MD025 -->
+
 # 07 — Deployment View
 
 ## Deployment Topology
@@ -23,8 +25,8 @@ The infrastructure components for the application include:
 - **Database Server**: PostgreSQL database for persisting application data.
 - **Static File Server**: Serves static assets such as CSS, JavaScript, and image files.
 - **Reverse Proxy (optional)**: An Nginx or Apache server can be used as a reverse proxy.
-- **CI/CD Pipeline (optional)**: Automated deployment pipelines can be set up using tools like GitHub Actions.
-- **Containerization (optional)**: Docker can be used to containerize the application.
+- **Containerization**: Docker images are generated via the repository `Dockerfile`, using a multi-stage build to keep the final runtime minimal.
+- **CI/CD Pipeline**: Automated pipelines (Gitea Actions) run tests, build/push Docker images, and trigger deployments.
 - **Cloud Infrastructure (optional)**: The application can be deployed on cloud platforms.
 
 ## Environments
@@ -55,7 +57,32 @@ The production environment is set up for serving live traffic and includes:
 - Load balancer (e.g., Nginx) for distributing incoming requests
 - Monitoring and logging tools for tracking application performance
 
+## Containerized Deployment Flow
+
+The Docker-based deployment path aligns with the solution strategy documented in [04 — Solution Strategy](04_solution_strategy.md) and the CI practices captured in [14 — Testing & CI](14_testing_ci.md).
+
+### Image Build
+
+- The multi-stage `Dockerfile` installs dependencies in a builder layer (including system compilers and Python packages) and copies only the required runtime artifacts to the final image.
+- Build arguments are minimal; environment configuration (e.g., `DATABASE_URL`) is supplied at runtime. Secrets and configuration should be passed via environment variables or an orchestrator.
+- The resulting image exposes port `8000` and starts `uvicorn main:app` (s. [README.md](../README.md)).
+
+### Runtime Environment
+
+- For single-node deployments, run the container alongside PostgreSQL/Redis using Docker Compose or an equivalent orchestrator.
+- A reverse proxy (e.g., Nginx) terminates TLS and forwards traffic to the container on port `8000`.
+- Migrations must be applied prior to rolling out a new image; automation can hook into the deploy step to run `scripts/run_migrations.py`.
+
+### CI/CD Integration
+
+- Gitea Actions workflows reside under `.gitea/workflows/`.
+- `test.yml` executes the pytest suite using cached pip dependencies.
+- `build-and-push.yml` logs into the container registry, rebuilds the Docker image using GitHub Actions cache-backed layers, and pushes `latest` (and additional tags as required).
+- `deploy.yml` connects to the target host via SSH, pulls the pushed tag, stops any existing container, and launches the new version.
+- Required secrets: `GITEA_REGISTRY`, `GITEA_USERNAME`, `GITEA_PASSWORD`, `SSH_HOST`, `SSH_USERNAME`, `SSH_PRIVATE_KEY`.
+- Extend these workflows when introducing staging/blue-green deployments; keep cross-links with [14 — Testing & CI](14_testing_ci.md) up to date.
+
 ## Integrations and Future Work (deployment-related)
 
 - **Persistence of results**: `/api/simulations/run` currently returns in-memory results; next iteration should persist to `simulation_result` and reference scenarios.
-- **Deployment**: documentation focuses on local development; containerization and CI/CD pipelines remain to be defined. Consider Docker + GitHub Actions or a simple Docker Compose for local stacks.
+- **Deployment**: implement infrastructure-as-code (e.g., Terraform/Ansible) to provision the hosting environment and maintain parity across dev/stage/prod.