That works for relatively simple scenarios. When you have to add deploying sql changes or something having to update something in the cloud, you'd have to include a lot more plumbing.

▲

Yokohiii 2 hours ago | parent | next [-]

In my world CI/CD and db migrations are 2 different things working together. CI/CD at heart is rather simple for many setups. Migrations need quite a lot scrutiny, you really want to mess up there. But if you run on gihub actions with 50/50 uptime, does it matter?

▲

peheje 2 hours ago | parent | prev [-]

Deploying SQL changes? Why not just let the application do that on startup. Ofcourse be backward and forward compatible. SQL change only deploy.

"Update something in the cloud" <- What do you mean?

	▲	Yokohiii 2 hours ago \| parent [-]
		> Why not just let the application do that on startup. That only works on extremely simple setups and has risks. If you have only a single server, you can stall it. Now, how to roll back?