Get the latest tech news
Run Database in GitHub Actions, Persisting Data to S3, and Access It Publicly
When it comes to running a database for development, testing, demos, or short-lived workloads, cost and complexity can be big headaches. Traditional database hosting—like a VPS, a cloud VM, or a managed service—comes with ongoing costs, storage expenses, and configuration overhead. You often end up paying for resources even when you're not using them.
It sets up AWS credentials, starts WeSQL, waits for it to get ready, opens a tunnel, and then writes connection info to S3. Next time you run the workflow, WeSQL pulls data back from your chosen object storage provider (AWS S3, R2, or any S3-compatible service). You might never go back to your old ways of spinning up costly VMs or managed instances just to show someone a quick demo or run a batch of tests.
Or read this on Hacker News