Add protection for Prefect resource deployment?

[danilo-css]

Hello. When deploying the "Prefect" resource (a Apache airflow like resource for scheduling Python scripts) there's currently no built-in option to secure the resource when running a reverse proxy. This means that all my data in the resource will be exposed to the internet, effectively making it insecure.

Per deepseek:

If that's really it and I'm not missing something, a possible solution could be to add basic auth to the container labels. I myself didn't figure out how to do that since I don't understand Docker compose very well at the moment (suggestions welcome). It would be a nice addition to have protection built in on the resource in the future if that's really the case.

Anyone has some thoughts?

[danilo-css]

UPDATE: It seems the Prefect team itself is gonna add protection to the self deployment later in 2025. So no need for the Coolify team to worry about this. See PrefectHQ/prefect#2238 (comment) for details.

For users, just avoid deploying Prefect while this isn't available unless it's in a secured local network.