Database Port Forwarding

What problem will this feature address?

When I use the Dokploy DB service I am not able to expose a port to the host like in Docker Compose, unless of course I manually expose it through the command line. This would be useful as then we could still leverage the Dokploy build in backup and restore while providing a secure way to tunnel to the server without exposing the port to the public.

Describe the solution you'd like

I successful solution would be to add a field to allow us to forward ports to the host. Not just external like the current implementation.

Describe alternatives you've considered

I could manually run a docker service update
--publish-add target=5432,published=,protocol=tcp,mode=host

Problem is when I redeploy it gets wiped out.

Additional context

I may try and implement this when I have some time if nobody gets to it first.

Will you send a PR to implement it?

No

Start by tracing the Dokploy DB service configuration and redeploy path, comparing its current external port handling with Docker Compose and the stated docker service update command. Done means a host port-forwarding field is persisted through redeploys without requiring manual commands, with behavior verified for the supported database services.