Sek SakeudeungTanggung deh, kita bikin dashboard #grafana nya #litestream.
Lumayan jadi bisa sekalian pantau ukuran #sqlite nya #gotosocial instance ini.
Lapor kong @kongtol
#sqlite nya #gotosocial dah kelar dibikin replikasinya pake #litestream sesuai petunjuk dari doc-nya gts.
fredix 🐧#Litestream intéressant pour mettre en place une réplication en continue d'une base sqlite vers du S3, WebDav, etc
https://litestream.io
https://litestream.io
Reddit Tech VN BotFly.io giới thiệu tính năng Writable VFS mới trong Litestream, cải thiện quy trình sao lưu và phục hồi CSDL SQLite cho lập trình viên. #Litestream #SQLite #Flyio #Côngnghệ #Pháttriểnphầnmềm
https://www.reddit.com/r/programming/comments/1qqgjr9/litestream_writable_vfs/
Todd SundstedWrapping this thread up, v0.3.13 has been running without problem in production for the last ~3 days. Looks like I'm on the old version...
Ok, v0.5.6 of litestream didn't work—exact same problem (but new issue). I've installed v0.3.13 as my hail mary. Feature-wise litestream is exactly what I want for SQLite backups, so I'm happy to expend a few cycles, but at this point I'm looking at 2+ year old software. 🤷...
I just upgraded litestream on my epiktistes.com server from v0.5.3 to v0.5.6 and I am cautiously optimistic. v0.5.3 had a bug that filled up my storage, pegged the CPU, and generally broke my server by locking my ktistec database for 10-20 seconds at a time. I am posting this to deliberately test fate! C'mon... if you're gonna fail again, then fail and get it over with!
poes 🇵🇸#litestream eating 95% of my CPU, I think this is time to search for replacement.
Bryan 
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 asked #ChatGPT, and of course, it gave me nonsense to try. It even had me change the syntax of YAML from a single replica statement to an array of replicas with one entry. I later read that this was old ways of doing things in the 0.3.x series. So now I'll need to go back and fix before the old way is completely deprecated. 😑
I was so irritated I told ChatGPT the actual solution and then it tried to pretend that it was giving me the solution? 😡
ChatGPT also for some reason decided to use an AWS region (us-east-1) instead of Digital Ocean Spaces region(sfo3).
Anyway, in this journey, I also out of desperation asked #ChatGPT, and of course, it gave me nonsense to try. It even had me change the syntax of YAML from a single replica statement to an array of replicas with one entry. I later read that this was old ways of doing things in the 0.3.x series. So now I'll need to go back and fix before the old way is completely deprecated. 😑
I was so irritated I told ChatGPT the actual solution and then it tried to pretend that it was giving me the solution? 😡
ChatGPT also for some reason decided to use an AWS region (us-east-1) instead of Digital Ocean Spaces region(sfo3).
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 kept repeating until the .sqlite.db-litestream directory filled my disk (about 10x the size of actual DB). Still need to do sqlite backups the old fashioned way: make compressed copy and upload with s3cmd.
This kept repeating until the .sqlite.db-litestream directory filled my disk (about 10x the size of actual DB). Still need to do sqlite backups the old fashioned way: make compressed copy and upload with s3cmd.