On: Run Database in GitHub Actions, Persisting Data to...

[fire_lake]

Or just use Docker Compose?

[earayu → fire_lake]

Sure. That's the fascinating aspect of WeSQL database - its compute-storage separation allows you to run the database anywhere while data persists in S3.

You can shut down the compute service and restart it anywhere else - the data will simply restore from S3.

[fire_lake → earayu]

This sounds really interesting, but the article motivation is test databases.

Edit: suggest looking at this other post https://wesql.io/blog/every-database-will-be-rearchitectured...

[earayu → fire_lake]

Yep, GitHub Actions isn't meant for production deployment - it's a CI/CD service with a 6-hour limit per run.

But that's the cool thing about WeSQL - you can run it anywhere! Just fire it up like any other container. For production, throw it on ECS/EKS and you're good to go.

[ah27182 → fire_lake]

Yea, I’m not following why this approach is radically different from just doing that