Dokploy/website
1
0
Fork 0
mirror of https://github.com/Dokploy/website.git synced 2026-06-15 20:25:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: update Docker Compose utilities documentation

Browse Source 
- Clarified the functionality of Isolated Deployments, emphasizing automatic network handling.
- Added a warning callout regarding installation type considerations for custom installations, detailing potential issues after system restarts and the need for manual redeployment.
- Enhanced the Randomize Compose section with important notes on system restart implications and recommended approaches for different installation types.
This commit is contained in:
Mauricio Siu
2025-12-07 12:32:07 -06:00
parent f47045c824
commit 080a687084
1 changed files with 13 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
apps/docs/content/docs/core/docker-compose/utilities.mdx
View File

@@ -30,25 +30,27 @@ services:
When Isolated Deployments is enabled, Dokploy will:
1. Add a prefix to all your defined networks
2. Create a network based on your service's appName and associate it with each service in your compose file
1. Create a network based on your `appName` and associate it with each service in your compose file
2. Add the network to every service in your compose file
3. Connect the Traefik load balancer to this isolated network, maintaining service isolation while ensuring proper routing
When using this feature, you don't need to explicitly define dokploy-network in your networks section, as isolation is handled automatically.
## Randomize Compose
<Callout type="warn">
**Important: Installation Type Considerations**
Dokploy offers functionality to randomize various compose properties:
If you're using a **custom installation** that replaces the standalone Traefik container with a Docker service (see [Manual Installation](/docs/core/manual-installation)), be aware of the following risks:
1. Volumes
2. Networks
3. Services
4. Configs
5. Secrets
1. **System Restart Issues**: If your system restarts, your services may lose their network references to Traefik. This happens because Docker Swarm changes network references after a restart, which can cause connectivity issues between your services and Traefik.
2. **Manual Redeployment Required**: After a system restart, you may need to manually redeploy your Docker Compose applications to restore network connectivity, which can be tedious and time-consuming.
3. **Reference**: For more details about this issue, see [GitHub Issue #1004](https://github.com/Dokploy/dokploy/issues/1004).
**Recommended Approach**: If you use the **official installation** or **manual installation with the standalone Traefik container**, you won't experience these issues. Your services should start normally after a system restart without requiring manual intervention.
</Callout>
You can specify a custom prefix that will be used as a suffix for each compose property.
Note: If both Isolated Deployments and Randomize Compose are enabled, the Isolated Deployments configuration takes precedence.