Fosstodon

0 posts0 participants0 posts today

MaruJarang pake instance <a href="https://social.maru.my/tags/memos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#memos</a> yang update, soalnya masih make yang versi 0.22 karena settingan <a href="https://social.maru.my/tags/s3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#s3</a> nya masih masuk akal. Kalau pake R2 sih ga masalah, tapi kalo S3nya pake <a href="https://social.maru.my/tags/minio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#minio</a>, itu yang bikin repot.Tapi ada instance yang satu lagi yang sengaja saya bikin update karena ga pake settingan <a href="https://social.maru.my/tags/s3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#S3</a> tapi <a href="https://social.maru.my/tags/local" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#local</a> storage.Kalau update harus update <code>Dockerfile</code> dulu dan di push ke docker hub. Karena server untuk build sama server untuk host memos beda.Bagi yang mau make memos yang udah otomatis terinstall <a href="https://social.maru.my/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a> bisa gunakan image ini : <a href="https://hub.docker.com/r/putraeka/memos-litestream" rel="nofollow noopener noreferrer" target="_blank">https://hub.docker.com/r/putraeka/memos-litestream</a>

Bumble<a href="https://hachyderm.io/@markus" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@markus@hachyderm.io</a> <a href="https://thefedi.forum/category/8/gotosocial" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gotosocial@thefedi.forum</a> I've had to turn it off for now. It's continuing to eat disk space. I didn't know if I could just delete all those files or it would comprise the integrity of the mirror process. Very odd. I did try their support channel but no response in a week. I'm at a loss. Need to try and find a new solution. <a href="https://ibe.social/tags/litestream" rel="nofollow noopener noreferrer" target="_blank">#litestream</a>

BumbleAnyone using <a href="https://ibe.social/tags/litestream" rel="nofollow noopener noreferrer" target="_blank">#litestream</a> for an <a href="https://ibe.social/tags/sqlite" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a> DB I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a <code>generations</code> folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space. My config includes <code>retention: 24h</code> and <code>retention-check-interval: 1h</code> with a <code>snapshot-interval: 4h</code>. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream <a href="https://ibe.social/tags/GoToSocial" rel="nofollow noopener noreferrer" target="_blank">#GoToSocial</a> <a href="https://ibe.social/tags/gts" rel="nofollow noopener noreferrer" target="_blank">#gts</a> <a href="https://thefedi.forum/category/8/gotosocial" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gotosocial@thefedi.forum</a>

bumbleAnyone using <a href="https://gofer.social/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a> for an <a href="https://gofer.social/tags/sqlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a> DBI have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a <code>generations</code> folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.My config includes <code>retention: 24h</code> and <code>retention-check-interval: 1h</code> with a <code>snapshot-interval: 4h</code>. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream<a href="https://gofer.social/tags/gotosocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoToSocial</a> <a href="https://gofer.social/tags/gts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gts</a>

Markus 🤓✨I am continuously amazed how far you can get with ancient tech stacks. :D My ARM-based VPS at Hetzner, with all my <a href="https://hachyderm.io/tags/GoLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoLang</a> web apps, using <a href="https://hachyderm.io/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> with <a href="https://hachyderm.io/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a> for streaming replication, has had zero downtime for over a year now.

lucianosoooo close to getting my evil <a href="https://parens.social/tags/datomic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datomic</a> on <a href="https://parens.social/tags/sqlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a>+<a href="https://parens.social/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a> idea running and I’m now running into an undebuggable fly.io error 😵‍💫😭

BH2Just released an update that uses django-registration to require email verification, django-honeypot to prevent spam signups, and <a href="https://just.systems" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://just.systems</a><a href="https://github.com/piepworks/blaze-starter/releases/tag/v2.5.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/piepworks/blaze-starter/releases/tag/v2.5.0</a><a href="https://mastodon.social/tags/Django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Django</a> <a href="https://mastodon.social/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a> <a href="https://mastodon.social/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> <a href="https://mastodon.social/tags/IndieWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IndieWeb</a>

爪卂尺ㄩ :kool:Kepikiran buat backup db <a href="https://eka.rodeo/tags/gotosocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gotosocial</a> pake <a href="https://eka.rodeo/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a>, cuma dbnya udah hampir 2GB, itu di <a href="https://eka.rodeo/tags/backblaze" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backblaze</a> nanti jadi brp GB?

TobiHooray! I'm so happy right now. I finally managed to get Django, django-q2, and litestream (S3 replication) working on CapRover in a single container running with s6-overlay. I've been at this for days now.<a href="https://fosstodon.org/tags/django" class="mention hashtag" rel="tag">#django</a> <a href="https://fosstodon.org/tags/litestream" class="mention hashtag" rel="tag">#litestream</a>

postmodernI know sqlite3 has become popular again. Has anyone looked at litestream? It can apparently distribute/replicate sqlite3 databases. <a href="https://litestream.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://litestream.io/</a> <a href="https://ruby.social/tags/sqlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a> <a href="https://ruby.social/tags/sqlite3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite3</a> <a href="https://ruby.social/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a>

André Hoarau<a href="https://fosstodon.org/@lawik" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lawik</a> By the way, I also use their S3 Object Storage service to backup the <a href="https://floss.social/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> database using <a href="https://floss.social/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a> and <a href="https://floss.social/tags/rclone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rclone</a> (for encryption).

Trey PiepmeierTrying out Backblaze B2 to store my <a href="https://indieweb.social/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a> SQLite streaming backups rather than DigitalOcean Spaces. So far, so good, and probably going to be free for a loong time!

Paul Rohr<a href="https://fosstodon.org/@chrisg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chrisg</a> If you had to rank them in order, which aspects are most/least important to your vision?- storage engine - replication protocol(s) - backup / resilience mechanisms - query / indexing modes - primary means of access (web, SQL, ...) - licenseDo you see this falling somewhere on the <a href="https://hachyderm.io/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> / <a href="https://hachyderm.io/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a> / <a href="https://hachyderm.io/tags/LiteFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LiteFS</a> spectrum, or are you envisioning a new greenfield project?

BH2Version 2 is out and ready to try! We’ve got <a href="https://mastodon.social/tags/Playwright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Playwright</a>! We’ve got <a href="https://mastodon.social/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a>! We’re all in on <a href="https://mastodon.social/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> and <a href="https://mastodon.social/tags/FlyIo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FlyIo</a>! It’s totally free for personal (non-commercial) use!Grab a copy while it’s fresh <a href="https://github.com/piepworks/blaze-starter" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/piepworks/blaze-starter</a><a href="https://mastodon.social/tags/Django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Django</a> <a href="https://mastodon.social/tags/BlazeHorse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlazeHorse</a> <a href="https://mastodon.social/tags/ProgressiveEnhancement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProgressiveEnhancement</a>

Trey PiepmeierWell, this sure is neat. <a href="https://fly.io/blog/litefs-cloud/" rel="nofollow noopener noreferrer" target="_blank">https://fly.io/blog/litefs-cloud/</a>I’ll be very curious to see how much it ends up costing.<a href="https://indieweb.social/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> <a href="https://indieweb.social/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a> <a href="https://indieweb.social/tags/LiteFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LiteFS</a>

wilson 🍜after wrapping some deployments of <a href="https://hachyderm.io/tags/sqlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a> apps with <a href="https://hachyderm.io/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a> last weekend, it's a lot of fun to delete kubernetes pods and see that it resumes like nothing happened, despite the lack of external database or persistent volumes

wilson 🍜i feel like <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> problems would be much simpler if all apps just use <a href="https://hachyderm.io/tags/sqlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a> paired with <a href="https://hachyderm.io/tags/litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litestream</a>, then consolidate management of storage with minio 🤔 gonna try it out

FErki<a href="https://babka.social/@serge" class="u-url mention">@serge</a> The Litestream website has a nice overview of similar alternatives: <a href="https://litestream.io/alternatives/" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://litestream.io/alternatives/</a>Quite nice selection for various priorities and trade-offs.TL;DR: - <a href="https://fosstodon.org/tags/Litestream" class="mention hashtag" rel="tag">#Litestream</a> is primarily for disaster recovery - <a href="https://fosstodon.org/tags/LiteFS" class="mention hashtag" rel="tag">#LiteFS</a> is a distributed file system from the same authors for "high availability and low global latency" - <a href="https://fosstodon.org/tags/rqlite" class="mention hashtag" rel="tag">#rqlite</a> (and <a href="https://fosstodon.org/tags/dqlite" class="mention hashtag" rel="tag">#dqlite</a>) "trades higher durability for lower write throughput"

Alejandro BaezAnd now a new one from Ben Johnson over <a href="https://fosstodon.org/tags/sqlite" class="mention hashtag" rel="tag">#sqlite</a>; <a href="https://fosstodon.org/tags/litefs" class="mention hashtag" rel="tag">#litefs</a>. Essentially a fuse fs for replication of sqlite with graceful leader election. I think this is pretty neat, though still like <a href="https://fosstodon.org/tags/litestream" class="mention hashtag" rel="tag">#litestream</a> more. Still, I already have <a href="https://fosstodon.org/tags/consul" class="mention hashtag" rel="tag">#consul</a> as my central everything anyway. Might as well play with this. 😎<a href="https://github.com/superfly/litefs" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/superfly/litefs</a>

Alejandro BaezEven with multi read replicas on <a href="https://fosstodon.org/tags/litestream" class="mention hashtag" rel="tag">#litestream</a>. Your system most likely doesn't need strong consistency. You can get by with having one writer. Publish events to some message broker. So the writer can do what it was destined to do.Leaving the rest of the app to keep turning. Updating once the read replicas synced from those writes.

Recent searches

Search options

Administered by:

Server stats:

#litestream