[Bug]: DragonflyDB Loses Public Port Configuration After Restart

[tbvgl]

Error Message and Logs

Issue: When restarting a DragonflyDB instance in Coolify, the public port setting is not retained. The instance loses its public port configuration, unlike PostgreSQL, which correctly restores the public port after a restart.

Logs: No specific error logs, but the issue can be observed when checking the network settings of the DragonflyDB container after a restart. Port mappings are missing or not marked as public.

Steps to Reproduce

1. Deploy a DragonflyDB instance in Coolify and make the port public.
2. Confirm that the port is accessible publicly (e.g., using curl or a browser).
3. Restart the DragonflyDB instance from the Coolify dashboard or CLI.
4. Check the network configuration of the DragonflyDB instance after the restart.
5. Observe that the public port setting is not retained, and the instance is no longer accessible publicly.

Example Repository URL

Not applicable. This issue can be reproduced using a default DragonflyDB instance setup in Coolify.

Coolify Version

v4.0.0-beta.367

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

The issue does not occur with PostgreSQL instances, where the public port is restored correctly after a restart. The bug seems specific to DragonflyDB. Attempts to resolve it by adding a save() call in the StartDragonfly.php script did not fix the problem. This suggests that the is_public and public_port attributes may not be set or persisted correctly before the StartDatabaseProxy call.