Regression in v0.30.2: Traefik does not start after server reboot

To Reproduce

1. Install Dokploy v0.30.2 on a fresh server.
2. Verify that Dokploy and its managed URLs are working correctly.
3. Restart the server: sudo reboot
4. After the server comes back online, check the running containers: docker ps
5. Inspect the Dokploy network: docker network inspect dokploy-network
6. Observe that Dokploy and PostgreSQL are running, while Traefik is not running or is not correctly connected/available.

Current vs. Expected behavior

Current: Traefik works correctly immediately after the initial installation, but after a server reboot it does not start correctly. Dokploy and PostgreSQL restart normally, but because Traefik is unavailable, all applications and domains routed through Traefik become inaccessible.

Expected: Traefik should automatically restart after a server reboot and remain connected to dokploy-network. All Dokploy-managed applications and domains should remain accessible after the reboot without requiring manual intervention.

Suspected cause: In v0.29.13, the install script explicitly ran docker network connect dokploy-network dokploy-traefik after creating the Traefik container. This command appears to be missing from the v0.30.2 install script, which may explain why Traefik loses its network connection after a reboot.

Provide environment information

- Dokploy: v0.30.2
- Traefik: v3.6.7
- Docker: Docker Swarm
- OS: Ubuntu

Which area(s) are affected? (Select all that apply)

Traefik, Installation

Are you deploying the applications where Dokploy is installed or on a remote server?

Both

Additional context

A possible fix would be to restore the docker network connect dokploy-network dokploy-traefik command after Traefik container creation, and optionally verify the connection before completing installation, e.g.:

docker network inspect dokploy-network --format '{{range .Containers}}{{.Name}}{{"\n"}}{{end}}' | grep -q '^dokploy-traefik$'

A longer-term alternative could be running Traefik as a Docker Swarm service (like Dokploy and PostgreSQL) for more consistent lifecycle management.

Will you send a PR to fix it?

No

Compare the v0.30.2 install script with the v0.29.13 version, focusing on Traefik creation and its connection to dokploy-network. Reproduce the issue with a reboot, then use docker ps and docker network inspect dokploy-network to verify that Traefik restarts, remains connected, and managed applications and domains stay accessible.