[Bug]: UX regression when enabling proxy for database service

[gabrieljablonski]

Error Message and Logs

In previous versions, you could type the port into the "Proxy" > "Port" field and click "Make it publicly available" directly to save and expose the port directly.

Now, you must type the port, and first scroll back up to save the service, before checking the option.

Steps to Reproduce

1. Create a database service (e.g. Postgres)
2. Deploy the service
3. Type out the port under the Proxy section
4. Click "Make it publicly available"

Example Repository URL

No response

Coolify Version

v4.0.0-beta.441

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

Please revert back to previous behavior.

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Remove the disabled attribute from the publicPort input across PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, ClickHouse, and Service database configuration views so users can enter a port and enable public access in one action and have both saved together via instantSave.

• Remove the disabled="{{ $isPublic }}" / disabled="{{ $database->is_public }}" binding from the publicPort <x-forms.input> across ClickHouse, Dragonfly, KeyDB, PostgreSQL, and the service database view so the Public Port input is no longer automatically disabled when a database is marked public.

• ✅ Create PR with these edits
• 📋 Get copyable edits