Proposals

What problem will this feature address?

Good morning,

I recently discovered your project and I must say it’s truly amazing!
I’m using Docker Swarm and, honestly, after searching the entire internet, I couldn’t find another solution like this.

While using Dokploy, I came across a few minor gaps/details which, in my opinion, could make it easier to use for others as well. I’d like to share them as suggestions:

1. Traefik

I’m already using my own preconfigured Traefik setup, because I need to use TLS Passthrough and sometimes a custom TLS resolver (StepCA), and occasionally Mantrae as a UI provider.

Because of this, I had to create my own Traefik container via docker stack. However, its name is generated by default as dokploy_traefik instead of dokploy-traefik.

It would be great to introduce an environment variable in Dokploy that controls the Traefik service name used in this file:
https://github.com/Dokploy/dokploy/blob/canary/apps/dokploy/server/api/routers/settings.ts

It would also be very useful if the network name (dokploy-network) could be configurable via an environment variable.

2. Application Name

Custom application names for compose/stack deployments:
After creating a project, there is currently no way to rename the application.

For some critical applications, I don’t want long auto-generated names. At the moment, changing the name requires modifying the PostgreSQL database directly, which is not ideal.

3. Project / Service Icons

There is no option to assign icons to Projects or Services.
This feature already exists when adding databases (e.g., PostgreSQL).

Something similar to this would be great:
https://gethomepage.dev/configs/services/#icons
https://dashboardicons.com/

4. Domains

It would be great if, when adding a domain, there was an option like:

“I use my own reverse proxy”

This option would disable the remaining Traefik-related settings, so the domain is visible in the panel but not handled by Dokploy’s Traefik. Optionally, it could also allow specifying the network the service should attach to.

This would be useful for setups using Cloudflare, Pangolin, or other reverse proxies without Traefik.

Thank you for this fantastic project and for all your hard work!
I hope these suggestions are helpful.

Describe the solution you'd like

described above

Describe alternatives you've considered

described above

Additional context

No response

Will you send a PR to implement it?

Yes

This issue bundles four proposals: configurable Traefik and network names in apps/dokploy/server/api/routers/settings.ts, application renaming, project and service icons, and reverse-proxy domain handling. First split the proposals into focused issues, then inspect settings.ts and the existing database icon flow. Done should be defined separately for each feature, including configuration behavior and UI changes.