Concerns about Project Configuration Management & lack of Git integration

[kvdb]

We recently migrated several of our apps to Coolify from Google App Engine/Cloud Run. Previously, we used a GitLab pipeline with gcloud CLI to deploy preview, staging, and production environments.

Switching to Coolify required adapting our workflow from CLI-based deployments to a Webhooks/PR-driven approach. While not ideal, we’ve made it work. It seems we’re not alone in our wish for additional features here: related discussion.

One major concern we have is configuration management. With our previous setup, nearly everything related to deployment was stored in Git (excluding credentials), effectively making it Infrastructure as Code (IaC). However, with Coolify, I recently heard a developer say, "I just need to add this command to the post-deployment hook."—which raised red flags for me.

I worry that project settings might be modified manually through the Coolify dashboard without others being aware, leading to deployment failures that could take days to troubleshoot. A potential solution would be allowing project configurations to be stored in Git and treated as read-only in the dashboard, preventing ad-hoc changes that aren’t tracked.

A related issue applies to the "Container Labels" settings (screenshot below). I have no way of knowing whether a developer manually changed these settings or if they are just defaults.

Is this a concern shared by others? And do the Coolify developers see this as something worth addressing in the roadmap?