Strongly needed. Vercel performs very well in this regard; every branch can have a separate deployment, and each deployment has its own independent domain.
I would like to suggest improving the deployment controls around the Service Status / Deployment area.
Currently, if I want to switch the deployment branch of a service, I need to go into the service settings, find the Source configuration, select another branch, save it, and then redeploy. This flow is understandable, but it feels a bit long when I need to test different branches, temporarily switch to another branch, or redeploy a specific version.
Since the current Source is already displayed on the Service Status page, it would be very convenient if it could also work as a quick action area.
Suggested controls:
One related detail I liked in Dokploy is that the deployment page makes the auto-deploy status very clear. For production services, it is useful to clearly control whether every code push should trigger a deployment.
This would make the deployment workflow smoother, especially when testing branches, switching temporarily, or redeploying specific versions.
Strongly needed. Vercel performs very well in this regard; every branch can have a separate deployment, and each deployment has its own independent domain.