Warn users in the UI about needing to add "dokploy-network" to all services when configuring a domain

[nktnet1]

For example, supposed the user defines this docker-compose for umami (copied from GitHub or a third party source rather than using an existing template, for demo purposes):

services:
  umami:
    image: ghcr.io/umami-software/umami:postgresql-latest
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "curl http://localhost:3000/api/heartbeat"]
      interval: 5s
      timeout: 5s
      retries: 5
    depends_on:
      db:
        condition: service_healthy
    environment:
      DATABASE_URL: postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}
      DATABASE_TYPE: postgresql
      APP_SECRET: ${APP_SECRET}

  db:
    image: postgres:17-alpine
    restart: always
    ports:
      - 9123:5432
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
      interval: 5s
      timeout: 5s
      retries: 5
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: ${POSTGRES_DB}
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}

volumes:
  db-data:

Then hits "deploy". Everything works as expected.

They then go and add a domain and re-deploy. Suddenly, their application can no longer connect to the database. Isn't immediately obvious why.

The reason is because Dokploy injects the following to the umami service (only visible when you click "preview compose":

    networks:
      - dokploy-network

but does not automatically do the same for the database.

---

Suggestions

When a domain is first configured:

1. Check and add dokploy-network automatically to all services if missing (probably not a good idea)
2. Check and add another local/private network to all services in the compose
3. In the domains tab, warn users about needing to add the "dokploy-network" to all services, and potentially a link to the documentations for docker-compose domain: https://docs.dokploy.com/docs/core/docker-compose/domains, e.g. alongside the blue highlight note below:
   

I think option 3 is probably the right approach.

[Siumauricio]

I agree, I think we should manage a toggle that automatically says if we want to add to all services the dokploy-network so it would automatically do everything and by default it would be enabled!