Conversation between myself and ChatGPT. Me: I found the problem. the new v0.5.3 release requires non-aws S3 to include the option sign-payload: true. for some reason this is no longer default as of v0.5.3, it was default through version v0.5.2. ChatGPT: Nice catch — that fits the symptom perfectly: SigV4 SignatureDoesNotMatch during multipart UploadPart is exactly what you see when the server expects a signed payload but the client is using UNSIGNED-PAYLOAD (or otherwise not including the payload hash in the signature). For anyone else hitting this on Litestream v0.5.3 + DigitalOcean Spaces (or other S3-compatible), the fix is to set sign-payload: true on the replica. example Yaml: dbs: - path: /gotosocial/sqlite.db replicas: - type: s3 bucket: dustyninja-backup path: db endpoint: https://sfo3.digitaloceanspaces.com region: us-east-1 sign-payload: true access-key-id: ${LITESTREAM_ACCESS_KEY_ID} secret-access-key: ${LITESTREAM_SECRET_ACCESS_KEY}

The #litestream issue I made generated a number of responses, and there was an option that changed from not required to required. (I'll spare you the explanation here since it's all in the above issue.) 😵‍💫

Anyway, in this journey, I also out of desperation […]

[Original post on dusty.ninja]

Original post on dusty.ninja

Tried to get #Litestream working again with #gotosocial but I keep running into 403 errors using #DigitalOcean Spaces for S3. the error is "api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method".

This […]

Durable Background Execution with Go and SQLite A DNS outage is like a flash flood. It hits you and disappears as if it were never there. “It was probably the DNS” became a meme. But, half the time, we do not know the exact cause. The outage is…

And in a twist of design, here's doing durable execution directly with #sqlite and an event bus framework in #golang called #watermill.

So just in case you all in go, this may be the way to go instead of #litestream. 😅

Litestream v0.5.0 is Here Same Litestream goodness but better, faster, stronger

#Litestream 0.5 is even more reason just to pick #sqlite. You can get pretty far with litestream and have it fully manageable for duplication.

Lower the N tier of your app. 😉

Hacker News discussed Litestream v0.5.0, exploring its uses, advantages, and comparisons to Postgres/MySQL. The debate covered deploying SQLite apps (e.g., Fly.io), replication, performance, and the trade-offs between simplicity and robustness in database choices. #Litestream 1/6

Litestream: Revamped Bringing in what we learned from LiteFS

#Litestream now does compaction. Using s3 condition writes. 😎

#consul is good, but complex when not in infra. Especially for #litefs. Too many moving parts. 😅

Very happy litestream is getting some love. Makes #sqlite even more of a no brainer choice. 😏

Overview: Hacker News discussed the revamped Litestream for SQLite replication. Key points: new features like wildcard replication & point-in-time recovery, various use cases, comparisons to Postgres, and integration with platforms like Fly.io. Excitement for simpler DB management! #Litestream 1/4

Litestream: Revamped Bringing in what we learned from LiteFS

Uuuh, news on the #litestream front for #SQLite! fly.io/blog/litestr...

I am continuously amazed how far you can get with ancient tech stacks. :D My ARM-based VPS at Hetzner, with all my #GoLang web apps, using #SQLite with #Litestream for streaming replication, has had zero downtime for over a year now.

The Tiny Stack (Astro, SQLite, Litestream) | LogSnag A simple, robust, and minimal stack for building web applications with Astro, SQLite, and Litestream.

Damn, I didn't know #litestream was so easy to setup! just set it up to backup all my production dbs in less than 10 minutes!
Followed The Tiny Stack article (logsnag.com/blog/the-tin...) but had to avoid the --exec section; might work really well for Node...