Update service ports to 12015 for backend and 12016 for frontend; adjust configurations and documentation accordingly

docs/7-deployment-view.md

@@ -13,7 +13,7 @@ Describes:
 │  ┌─────────────┐  ┌────────────────────┐   │
 │  │  frontend   │  │      backend       │   │
 │  │  (Flask)    │  │    (FastAPI)       │   │
-│  │  :12001     │  │    :12000          │   │
+│  │  :12016     │  │    :12015          │   │
 │  └──────┬──────┘  └─────────┬──────────┘   │
 │         │                   │              │
 │         └────────┬──────────┘              │
@@ -33,8 +33,8 @@ Describes:
 
 | Building Block  | Container / Process          | Port  |
 | --------------- | ---------------------------- | ----- |
-| Flask frontend  | `frontend`                   | 12001 |
-| FastAPI backend | `backend`                    | 12000 |
+| Flask frontend  | `frontend`                   | 12016 |
+| FastAPI backend | `backend`                    | 12015 |
 | DuckDB          | File on host (`data/app.db`) | —     |
 
 ## Infrastructure Level 2
@@ -50,25 +50,25 @@ All services are containerized and orchestrated with `docker compose`:
 │  │  Docker Network: app-network (bridge)                │   │
 │  │  ┌──────────────────────────────────────────────┐    │   │
 │  │  │ Backend Container (FastAPI)                  │    │   │
-│  │  │ - Port: 12000                                │    │   │
+│  │  │ - Port: 12015                                │    │   │
 │  │  │ - Service Name: backend                      │    │   │
 │  │  │ - Volume Mount: /app/data ← host/data/       │    │   │
 │  │  ├──────────────────────────────────────────────┤    │   │
 │  │  │ Frontend Container (Flask)                   │    │   │
-│  │  │ - Port: 12001                                │    │   │
+│  │  │ - Port: 12016                                │    │   │
 │  │  │ - Service Name: frontend                     │    │   │
 │  │  │ - Depends on: backend (health check)         │    │   │
 │  │  ├──────────────────────────────────────────────┤    │   │
 │  │  │ Nginx Container (Reverse Proxy)              │    │   │
 │  │  │ - Port: 80 (HTTP), 443 (HTTPS)               │    │   │
 │  │  │ - Config: nginx/docker-compose.conf          │    │   │
-│  │  │ - Routes: /api/* → backend:12000             │    │   │
-│  │  │           / → frontend:12001                 │    │   │
+│  │  │ - Routes: /api/* → backend:12015             │    │   │
+│  │  │           / → frontend:12016                 │    │   │
 │  │  └──────────────────────────────────────────────┘    │   │
 │  └──────────────────────────────────────────────────────┘   │
 │                         ▲                                   │
 │                  Host Port Bindings                         │
-│         80:80, 443:443, 12000:12000, 12001:12001            │
+│         80:80, 443:443, 12015:12015, 12016:12016            │
 └─────────────────────────────────────────────────────────────┘
                          │
                       Users / Internet
@@ -79,7 +79,7 @@ All services are containerized and orchestrated with `docker compose`:
 1. Ensure Docker and Docker Compose are installed
 2. Create `.env` with required environment variables
 3. Run: `docker compose up --build`
-4. Access via browser at `http://localhost:12001` or through Nginx at `http://localhost:80`
+4. Access via browser at `http://localhost:12016` or through Nginx at `http://localhost:80`
 
 **Benefits:**
 
@@ -87,7 +87,7 @@ All services are containerized and orchestrated with `docker compose`:
 - **Simplicity**: Single command to start entire stack
 - **Portability**: Run on any system with Docker installed
 - **Persistence**: DuckDB data survives container restarts via volume mounts
-- **Networking**: Service names enable automatic DNS resolution (backend:12000, frontend:12001)
+- **Networking**: Service names enable automatic DNS resolution (backend:12015, frontend:12016)
 - **Observability**: Easy logging with `docker compose logs`
 
 **See**: [Docker Compose Deployment Guide](./deployment/docker-compose.md) for detailed instructions.
@@ -101,6 +101,6 @@ If using Coolify instead of Docker Compose:
 3. **Data Persistence**: Named volume keeps DuckDB data at `/app/data`
 4. **Fallback Path**: Use separate Nixpacks services only when one-stack Compose deploy is not suitable
 
-**Note**: In Compose-based Coolify deployment, frontend reaches backend through Docker DNS at `http://backend:12000`. In Nixpacks-based deployment, use Coolify internal networking or colocate both services.
+**Note**: In Compose-based Coolify deployment, frontend reaches backend through Docker DNS at `http://backend:12015`. In Nixpacks-based deployment, use Coolify internal networking or colocate both services.
 
 **See**: [Coolify Deployment Guide](./deployment/coolify.md) for detailed instructions.