Runtime Environments Guide

The environment tree supplies both active Swarm launchers and retained Compose launchers. Split Swarm stacks may load more than one service-local env file.

Source Of TruthCopy Anchor Link

• VPS layout is the source of truth for folder structure and variable names.
• Non-production environments should copy the same structure and replace only env values.
• Compose files do not change per environment.

Directory ModelCopy Anchor Link

runtime/
  stacks/
    infrastructure/
    services/
  environments/
    dev/
      infrastructure/
      services/
    vps/
      infrastructure/
      services/

File TypesCopy Anchor Link

VPSCopy Anchor Link

• Local live runtime values: runtime/environments/vps/**/.env
• Tracked placeholder values: runtime/environments/vps/**/*{service}.env

The launcher scripts use the local .env file first. If it does not exist, they fall back to the tracked placeholder file.

DEVCopy Anchor Link

• Tracked reusable templates: runtime/environments/dev/**/*.dev.env

The launcher scripts use these files directly when you run them with dev.

Infrastructure Environment PathsCopy Anchor Link

• Edge:
  • runtime/environments/vps/infrastructure/edge/traefik/.env
  • runtime/environments/vps/infrastructure/edge/portainer/.env
  • runtime/environments/vps/infrastructure/edge/kener/.env
• Platform:
  • runtime/environments/vps/infrastructure/platform/.env
• Operations:
  • runtime/environments/vps/infrastructure/operations/.env
• Registry:
  • runtime/environments/vps/infrastructure/registry/.env
• Feeds:
  • runtime/environments/vps/infrastructure/feeds/.env
• Gateway:
  • runtime/environments/vps/infrastructure/gateway/.env
• NetBird:
  • runtime/environments/vps/infrastructure/netbird/.env
• Databases:
  • runtime/environments/vps/infrastructure/databases/{mssql,postgres,mysql,mongodb}/.env
• Object storage:
  • runtime/environments/vps/infrastructure/object-storage/rustfs/.env

The matching dev templates live under runtime/environments/dev/infrastructure/**.

Service Environment PathsCopy Anchor Link

• Perspective-V core:
  • runtime/environments/vps/services/perspective-v.com/identity.perspective-v.com/.env
  • runtime/environments/vps/services/perspective-v.com/graph.perspective-v.com/.env
  • runtime/environments/vps/services/perspective-v.com/console.perspective-v.com/.env
• Domain sites:
  • runtime/environments/vps/services/dbskc.com/dbskc.com/.env
  • runtime/environments/vps/services/nishatcolony.pk/nishatcolony.pk/.env
  • runtime/environments/vps/services/arnexglobal.com/data.arnexglobal.com/.env
• Starter domains:
  • runtime/environments/vps/services/syassociates.pk/syassociates.pk/syassociates.pk.env plus optional local .env
  • runtime/environments/vps/services/syassociates.pk/service.syassociates.pk/service.syassociates.pk.env plus optional local .env

The matching dev templates live under runtime/environments/dev/services/**.

Swarm DEV CoverageCopy Anchor Link

The role-organized Swarm launchers map each workload to a tracked DEV template, including the split Perspective-V services and WordPress-backed websites. Run the matching swarm/scripts/** launcher with config dev before deployment.

Rebuild A New Docker EnvironmentCopy Anchor Link

1. Keep the compose files unchanged.
2. Start from the matching file under runtime/environments/dev.
3. Replace hostnames, passwords, image tags, and bind settings for the new environment.
4. Use the launcher scripts in dev mode.

Examples:

./runtime/scripts/infrastructure/edge-traefik.sh show dev
./runtime/scripts/infrastructure/edge-traefik.sh config dev
./runtime/scripts/infrastructure/platform.sh up dev
./runtime/scripts/services/identity.sh up dev

Recommended WorkflowCopy Anchor Link

For the VPS:

cp runtime/environments/vps/infrastructure/platform/platform.env runtime/environments/vps/infrastructure/platform/.env
nano runtime/environments/vps/infrastructure/platform/.env
./runtime/scripts/infrastructure/platform.sh up

For a reproducible non-production host:

nano runtime/environments/dev/infrastructure/platform/platform.dev.env
./runtime/scripts/infrastructure/platform.sh up dev