News for hackers. Stuff that matters.
Re:GitHub Actions down again today by starik36 on Tuesday May 26, 2026 @10:55AM (#48280700)
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.
Re:GitHub Actions down again today by Yokohiii on Tuesday May 26, 2026 @11:20AM (#48281029)
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?
Re:GitHub Actions down again today by peheje on Tuesday May 26, 2026 @11:07AM (#48280864)
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?

Re:GitHub Actions down again today by Yokohiii on Tuesday May 26, 2026 @11:24AM (#48281082)
> 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?

Re:GitHub Actions down again today by peheje on Tuesday May 26, 2026 @03:10PM (#48284450)
We try to keep things simple. Everything has risks. No stall, run async, backward compatible. DB handles rollback via transactions. Happy to expand if interested.
Re:GitHub Actions down again today by bob1029 on Tuesday May 26, 2026 @01:32PM (#48282919)
Deploying SQL changes is actually trivial if you are using SQLite.

I agree in a hosted+shared SQL scenario you have to be a little bit more careful with all of this. Arguably, you should have a separate schema management phase in these cases.

But if you are just SQLite embedded in the service, you can use the user_version pragma to track schema version and perform deterministic migrations (assuming a user didn't manually jack with the file in-between).