Be able to change BASE_PATH and TRAEFIK_PATH

What problem will this feature address?

Hi there ! What a great project :)

Here is my requirements for on-premise usage :

• as an old server admin, I have tons of docker-compose.yaml projects with Traefik labels set on them
• as a new Dokploy user, I would like to keep my Traefik config separately from Dokploy

Describe the solution you'd like

For that, the need is to :

• have possibility to set dokploy BASE_PATH as environment variable
• have possibility to set dokploy MAIN_TRAEFIK_PATH and DYNAMIC_TRAEFIK_PATH as environment variable, and independently of BASE_PATH
• have a docker-compose.yml dokploy installation file (with swarm compatibility), with and without Traefik, and a .env.example

Describe alternatives you've considered

For now I've just created my own Dokploy docker-compose.yml with Traefik labels used by my own Traefik, and used the default /etc/dokploy as storage.

With this dokploy instance, I can deploy my projects throught docker-compose Dokpoy's feature and Git code 👍️

Additional context

No response

Will you send a PR to implement it?

No

Start by locating the current BASE_PATH, MAIN_TRAEFIK_PATH, and DYNAMIC_TRAEFIK_PATH configuration and the deployment manifests. Add or update docker-compose.yml, including Swarm-compatible variants with and without Traefik, and provide a .env.example. Done means all three paths can be configured independently through environment variables and the documented compose options support the requested on-premise setup.