Feedback on Preview Deployments with Supabase + React Stack: Critical Issues Blocking Usability

[bmajkut]

Hi Coolify team and community,

I'm opening this thread to share my experiences with the Preview Deployments feature, specifically when using a multi-service setup with Supabase (backend services like auth, db, etc.) and a React frontend. As a developer relying on Coolify for quick previews during PR workflows, I've hit several roadblocks that make this feature unreliable for complex Docker Compose projects. My goal is to provide detailed feedback to help improve it – I'd love to hear if others face the same issues, workarounds, or if fixes are planned!

Here are the key problems I've encountered (tested on latest Coolify version with a standard Supabase + React compose setup):

1. No volume cleanup on preview deletion: Deleting a preview deployment leaves dangling volumes from services (e.g., Supabase Postgres data dirs). This bloats storage and risks data leaks across previews. Suggestion: Auto-prune volumes on delete, like docker volume prune integration.
2. Pushed commits to PR branch don't trigger redeploy: New commits pushed to the Git branch tied to a PR don't auto-redeploy the preview. Manual intervention required every time. Suggestion: Watch branch for pushes like main deployments do.
3. No per-service domain templates in docker-compose.yaml: Can't define custom domain templates (e.g., service.project.preview.coolify.io) directly in compose for previews. Forces manual overrides.
4. General deployment domain format bleeds into previews (path prefix only): If main deployment uses /api path for a service, previews inherit it – but not full domain logic. Inconsistent and breaks Supabase paths.
5. No subdomain templates for preview services: Impossible to set subdomains like studio.preview.project.coolify.io for Supabase Studio. Preview Studio never starts properly without custom hacks.
6. Can't start preview if main deployment is stopped: Previews are blocked entirely if the base deployment is paused. Limits testing in paused prod-like envs.
7. Preview service domains get overwritten on redeploy: Even after editing/saving custom domains for preview services, they revert on any redeploy.
8. No granular control over services/containers: Can't stop, restart, or start individual services/containers in a preview (e.g., restart just Supabase db without full redeploy).
9. Previews ignore compose.yaml from PR branch: Always pulls from base/main instead of the actual PR branch's compose file. Breaks testing compose changes in PRs.

These issues make Preview Deployments unusable for anything beyond trivial single-service apps – especially with stateful services like Supabase. It's frustrating when PR previews should be a killer feature for teams!

Has anyone found workarounds (e.g., custom scripts for volumes)? Are these on the roadmap? Happy to provide compose.yaml snippets, logs, or help test fixes.

Thanks for building Coolify – let's make previews rock-solid! 🚀