Re:Run Database in GitHub Actions, Persisting Data to S3, an...
by fire_lake on Thursday December 12, 2024 @03:46AM
(#42397419)
Or just use Docker Compose?
[ Parent
| on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an...
by earayu on Thursday December 12, 2024 @03:48AM
(#42397428)
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.
Re:Run Database in GitHub Actions, Persisting Data to S3, an...
by fire_lake on Thursday December 12, 2024 @03:49AM
(#42397437)
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...
Re:Run Database in GitHub Actions, Persisting Data to S3, an...
by earayu on Thursday December 12, 2024 @03:55AM
(#42397470)
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.