Support Defining Applications as Part of a Compose Setup

What problem will this feature address?

Currently, deploying microservices on Dokploy is challenging because services often depend on each other. To ensure all services are deployed atomically and remain in sync, a Docker Compose setup is ideal. However, defining a Compose in Dokploy leads to a cluttered configuration: for example, the Env tab requires merging all environment variables from multiple services into one tab, some Compose features are limited or missing, and you end up with a really huge Docker Compose file. This makes managing microservices less clean and harder to maintain.

Describe the solution you'd like

Allow applications to be assigned to a Docker Compose setup. You can define each application as usual and then link it to a pre-defined Compose. Deploying the Compose will then deploy all linked services atomically, keeping them in sync and simplifying management.

Describe alternatives you've considered

Currently, each service is defined as a separate application and deployed using the recently added bulk deploy feature. However, this does not achieve true atomic deployment, as services can still go out of sync.

Additional context

No response

Will you send a PR to implement it?

No

Start by reviewing Dokploy’s existing Docker Compose handling and the recently added bulk deploy feature described in the issue. Determine where applications and Compose setups are modeled and deployed, then define how linked applications should deploy atomically; completion should support assigning applications to a predefined Compose and deploying the linked services together.