Runtime Wrapper Scripts Guide

The runtime launchers under runtime/scripts exist so you do not have to repeat full docker compose --env-file ... -f ... commands.

LocationsCopy Anchor Link

• Infrastructure: runtime/scripts/infrastructure
• Services: runtime/scripts/services
• Shared helpers: runtime/scripts/common

Use .sh on Linux/macOS and .bat on Windows.

Default Resolution RulesCopy Anchor Link

1. Default environment is vps.
2. In vps mode, the launcher uses the local .env file when it exists.
3. If the local .env file does not exist, the launcher uses the tracked placeholder env file.
4. In dev mode, the launcher uses the tracked *.dev.env file.

Supported ActionsCopy Anchor Link

• show
• up
• restart
• down
• pull
• logs
• ps
• config
• compose <raw args...>

Common ExamplesCopy Anchor Link

./runtime/scripts/infrastructure/platform.sh show
./runtime/scripts/infrastructure/platform.sh show dev
./runtime/scripts/infrastructure/registry.sh up registry-admin
./runtime/scripts/infrastructure/postgres.sh compose vps --profile admin up -d pgadmin
./runtime/scripts/services/identity.sh restart
./runtime/scripts/services/syassociates-web.sh show

Windows equivalents:

runtime\scripts\infrastructure\platform.bat show
runtime\scripts\infrastructure\platform.bat show dev
runtime\scripts\infrastructure\registry.bat up registry-admin
runtime\scripts\infrastructure\postgres.bat compose vps --profile admin up -d pgadmin
runtime\scripts\services\identity.bat restart
runtime\scripts\services\syassociates-web.bat show

Infrastructure LaunchersCopy Anchor Link

• edge-traefik
• edge-portainer
• edge-kener
• platform
• operations
• registry
• feeds
• gateway
• netbird
• rustfs
• mssql
• postgres
• mysql
• mongodb

Service LaunchersCopy Anchor Link

• identity
• graph
• console
• dbskc
• dbskc-wordpress
• nishatcolony
• nishatcolony-new
• arnexglobal-data
• syassociates-web
• syassociates-service

Recommended Usage PatternCopy Anchor Link

1. Run show first.
2. Run config if you want Docker Compose to render the final config.
3. Run up or restart.
4. Use ps and logs to verify the result.

Example:

./runtime/scripts/infrastructure/feeds.sh show
./runtime/scripts/infrastructure/feeds.sh config
./runtime/scripts/infrastructure/feeds.sh up
./runtime/scripts/infrastructure/feeds.sh ps
./runtime/scripts/infrastructure/feeds.sh logs