Provider Docker Compose

What Docker Compose Owns

The Provider stack is usually started as a small group of containers: the Provider gateway, required storage, cache or queue infrastructure, and optional local administration tools. The concrete service names, ports, volumes, and environment variables are deployment-specific and should be read from the owning repository.

Expected Shape

A Provider compose file normally defines:

• the Provider application container;
• persistent data services required by that Provider version;
• local-only admin tools when they are enabled;
• private volumes for configs, certificates, and credentials;
• a private network shared by the stack.

Public Rules

• Do not publish real secrets, exchange keys, private certificate paths, or local machine paths.
• Do not expose internal data stores as public integration surfaces.
• Studio should connect to the HTTPS Provider gateway, not to individual downstream containers.
• Keep the public website at the architecture level; keep executable compose details in the Provider repository.

For the current runnable compose file and exact environment contract, use the Provider deployment docs in trading.apps.