Development Environment Deployment Report
This report provides an overview of all applications and services deployed in the dev environment.
Generated: 2025-09-01T05:11:19.208866
Environment: dev
Total Applications: 12
Total Services: 35
Executive Summary
This dev environment contains 12 applications running a total of 35 services. On average, each application consists of 2.9 services.
Quick Stats
| Metric | Value | What this means |
|---|---|---|
| Applications | 12 | Number of distinct software projects deployed |
| Services | 35 | Total number of running software components |
| Average Complexity | 2.9 services per app | How many components each application typically has |
Applications Overview
Each application may consist of multiple services (like web server, database, cache, etc.)
| Application Name | Services | Network Connections | Data Storage | Description |
|---|---|---|---|---|
| heslb | 5 | swarm_traefik_network, pg_cluster_network (+1 more) | 2 storage volumes | Complex application with many components |
| skypay | 4 | swarm_traefik_network, pg_cluster_network (+1 more) | No persistent storage | Complex application with many components |
| flex-shopping | 1 | swarm_traefik_network, pg_cluster_network | 1 storage volumes | Simple single-service application |
| seri | 2 | swarm_traefik_network, pg_cluster_network (+1 more) | No persistent storage | Multi-service application |
| flex-food | 1 | swarm_traefik_network, pg_cluster_network | 1 storage volumes | Simple single-service application |
| auth | 2 | swarm_traefik_network, pg_cluster_network | 1 storage volumes | Multi-service application |
| flex-cargo | 4 | swarm_traefik_network, pg_cluster_network (+1 more) | 1 storage volumes | Complex application with many components |
| pg | 2 | swarm_traefik_network, pg_cluster_network | 4 storage volumes | Multi-service application |
| redis | 7 | redis_cluster_network | 8 storage volumes | Complex application with many components |
| mail-sender | 1 | swarm_traefik_network | No persistent storage | Simple single-service application |
| flex-delivery | 3 | swarm_traefik_network, pg_cluster_network (+1 more) | 1 storage volumes | Multi-service application |
| skypesa | 3 | swarm_traefik_network, pg_cluster_network (+1 more) | No persistent storage | Multi-service application |
Detailed Application Information
🔹 heslb
This application consists of 5 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network, redis_cluster_network
Data Storage: Uses 2 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| backend_main | heslb-backend-main | 1 (single instance) | 18 settings (complex) | Web accessible |
| backend_sentiment | heslb-backend-sentiment | 1 (single instance) | 6 settings (complex) | Not web accessible |
| frontend_web | heslb_sky-web | 1 (single instance) | 7 settings (complex) | Web accessible |
| mongodb | mongo | 1 (single instance) | Default settings | Not web accessible |
| qdrant | qdrant | 1 (single instance) | 1 custom settings | Not web accessible |
🔹 skypay
This application consists of 4 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network, redis_cluster_network
Data Storage: No persistent data storage (stateless application)
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| skypay-web | skypay-web | 1 (single instance) | 2 custom settings | Web accessible |
| skypay | skypay | 1 (single instance) | 22 settings (complex) | Web accessible |
| skypay-celery | skypay | 1 (single instance) | 22 settings (complex) | Not web accessible |
| skypay-celery-beat | skypay | 1 (single instance) | 22 settings (complex) | Not web accessible |
🔹 flex-shopping
This application consists of 1 service working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network
Data Storage: Uses 1 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| shopping-app | shopping-app | 1 (single instance) | 13 settings (complex) | Web accessible (3 routes) |
🔹 seri
This application consists of 2 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network, redis_cluster_network
Data Storage: No persistent data storage (stateless application)
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| seri-backend | seri_backend | 1 (single instance) | 6 settings (complex) | Web accessible |
| seri-frontend | seri_frontend | 1 (single instance) | 5 custom settings | Web accessible |
🔹 flex-food
This application consists of 1 service working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network
Data Storage: Uses 1 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| food-app | food-app | 1 (single instance) | 13 settings (complex) | Web accessible (3 routes) |
🔹 auth
This application consists of 2 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network
Data Storage: Uses 1 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| keycloak | iam | 1 (single instance) | 9 settings (complex) | Web accessible |
| auth-api-ext | sana_keycloak_node | 1 (single instance) | 9 settings (complex) | Web accessible |
🔹 flex-cargo
This application consists of 4 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network, redis_cluster_network
Data Storage: Uses 1 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| cargo-web | sana_web | 1 (single instance) | Default settings | Web accessible |
| cargo-app | cargo-app | 1 (single instance) | 17 settings (complex) | Web accessible (4 routes) |
| celery-worker | cargo-app | 1 (single instance) | 17 settings (complex) | Not web accessible |
| celery-beat | cargo-app | 1 (single instance) | 17 settings (complex) | Not web accessible |
🔹 pg
This application consists of 2 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network
Data Storage: Uses 4 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| postgres-primary | postgis | 1 (single instance) | 3 custom settings | Not web accessible |
| pgadmin | pgadmin4 | 1 (single instance) | 4 custom settings | Web accessible |
🔹 redis
This application consists of 7 services working together.
Network Access: Connected to redis_cluster_network
Data Storage: Uses 8 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| redis | redis | 1 (single instance) | Default settings | Not web accessible |
| redis-master | redis | 1 (single instance) | 1 custom settings | Not web accessible |
| redis-replica-1 | redis | 1 (single instance) | 1 custom settings | Not web accessible |
| redis-replica-2 | redis | 1 (single instance) | 1 custom settings | Not web accessible |
| redis-sentinel-1 | redis | 1 (single instance) | Default settings | Not web accessible |
| redis-sentinel-2 | redis | 1 (single instance) | Default settings | Not web accessible |
| redis-sentinel-3 | redis | 1 (single instance) | Default settings | Not web accessible |
🔹 mail-sender
This application consists of 1 service working together.
Network Access: Connected to swarm_traefik_network
Data Storage: No persistent data storage (stateless application)
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| mail-sender | mail-sender | 1 (single instance) | 9 settings (complex) | Web accessible |
🔹 flex-delivery
This application consists of 3 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network, redis_cluster_network
Data Storage: Uses 1 persistent storage volumes for data that needs to be kept between restarts
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| delivery-app | delivery-app | 1 (single instance) | 17 settings (complex) | Web accessible (4 routes) |
| delivery-celery-worker | delivery-app | 1 (single instance) | 17 settings (complex) | Not web accessible |
| delivery-celery-beat | delivery-app | 1 (single instance) | 17 settings (complex) | Not web accessible |
🔹 skypesa
This application consists of 3 services working together.
Network Access: Connected to swarm_traefik_network, pg_cluster_network, redis_cluster_network
Data Storage: No persistent data storage (stateless application)
Services Breakdown
Each service is a separate software component that handles specific tasks
| Service Name | Software Used | Instances | Configuration | Web Routes |
|---|---|---|---|---|
| skypesa-api-dev | skypesa-api | 1 (single instance) | 27 settings (complex) | Web accessible |
| celery | skypesa-api | 1 (single instance) | 27 settings (complex) | Not web accessible |
| celery-beat | skypesa-api | 1 (single instance) | 27 settings (complex) | Not web accessible |
Network Connectivity Overview
Networks allow applications to communicate with each other and shared services
| Network Name | Purpose | Connected Applications |
|---|---|---|
| pg_cluster_network | Database access (PostgreSQL) | heslb, skypay, flex-shopping, seri, flex-food, auth, flex-cargo, pg, flex-delivery, skypesa |
| redis_cluster_network | Cache and session storage | heslb, skypay, seri, flex-cargo, redis, flex-delivery, skypesa |
| swarm_traefik_network | Web traffic routing and load balancing | heslb, skypay, flex-shopping, seri, flex-food, auth, flex-cargo, pg, mail-sender, flex-delivery, skypesa |
Glossary
| Term | Definition |
|---|---|
| Service | A single software component (like a web server, database, or cache) |
| Application | A collection of services working together to provide functionality |
| Instance/Replica | How many copies of a service are running for redundancy or performance |
| Network | A virtual connection that allows services to communicate |
| Volume | Persistent storage that keeps data even when services restart |
| Port | A communication endpoint that allows external access to a service |
| Environment Variable | Configuration settings that control how a service behaves |