litestream
maddy
Our great sponsors
litestream | maddy | |
---|---|---|
165 | 30 | |
9,964 | 4,650 | |
- | - | |
7.5 | 8.0 | |
10 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
litestream
-
Ask HN: SQLite in Production?
I have not, but I keep meaning to collate everything I've learned into a set of useful defaults just to remind myself what settings I should be enabling and why.
Regarding Litestream, I learned pretty much all I know from their documentation: https://litestream.io/
-
How (and why) to run SQLite in production
This presentation is focused on the use-case of vertically scaling a single server and driving everything through that app server, which is running SQLite embedded within your application process.
This is the sweet-spot for SQLite applications, but there have been explorations and advances to running SQLite across a network of app servers. LiteFS (https://fly.io/docs/litefs/), the sibling to Litestream for backups (https://litestream.io), is aimed at precisely this use-case. Similarly, Turso (https://turso.tech) is a new-ish managed database company for running SQLite in a more traditional client-server distribution.
-
SQLite3 Replication: A Wizard's Guide🧙🏽
This post intends to help you setup replication for SQLite using Litestream.
-
Ask HN: Time travel" into a SQLite database using the WAL files?
I've been messing around with litestream. It is so cool. And, I either found a bug in the -timestamp switch or don't understand it correctly.
What I want to do is time travel into my sqlite database. I'm trying to do some forensics on why my web service returned the wrong data during a production event. Unfortunately, after the event, someone deleted records from the database and I'm unsure what the data looked like and am having trouble recreating the production issue.
Litestream has this great switch: -timestamp. If you use it (AFAICT) you can time travel into your database and go back to the database state at that moment. However, it does not seem to work as I expect it to:
https://github.com/benbjohnson/litestream/issues/564
I have the entirety of the sqlite database from the production event as well. Is there a way I could cycle through the WAL files and restore the database to the point in time before the records I need were deleted?
Will someone take sqlite and compile it into the browser using WASM so I can drag a sqlite database and WAL files into it and then using a timeline slider see all the states of the database over time? :)
-
Ask HN: Are you using SQLite and Litestream in production?
We're using SQLite in production very heavily with millions of databases and fairly high operations throughput.
But we did run into some scariness around trying to use Litestream that put me off it for the time being. Litestream is really cool but it is also very much a cool hack and the risk of database corruption issues feels very real.
The scariness I ran into was related to this issue https://github.com/benbjohnson/litestream/issues/510
-
Pocketbase: Open-source back end in 1 file
Litestream is a library that allows you to easily create backups. You can probably just do analytic queries on the backup data and reduce load on your server.
https://litestream.io/
- Litestream – Disaster recovery and continuous replication for SQLite
- Litestream: Replicated SQLite with no main and little cost
-
Why you should probably be using SQLite
One possible strategy is to have one directory/file per customer which is one SQLite file. But then as the user logs in, you have to look up first what database they should be connected to.
OR somehow derive it from the user ID/username. Keeping all the customer databases in a single directory/disk and then constantly "lite streaming" to S3.
Because each user is isolated, they'll be writing to their own database. But migrations would be a pain. They will have to be rolled out to each database separately.
One upside is, you can give users the ability to take their data with them, any time. It is just a single file.
[0]. https://litestream.io/
-
Monitor your Websites and Apps using Uptime Kuma
Upstream Kuma uses a local SQLite database to store account data, configuration for services to monitor, notification settings, and more. To make sure that our data is available across redeploys, we will bundle Uptime Kuma with Litestream, a project that implements streaming replication for SQLite databases to a remote object storage provider. Effectively, this allows us to treat the local SQLite database as if it were securely stored in a remote database.
maddy
-
Stalwart mail server (self-hosted all-in-one mail server) now as an admin webui
It's interesting how there is now
* Maddy: https://github.com/foxcpp/maddy
* Mox: https://github.com/mjl-/mox
* and Stalwart
which all see to aim for more or less the same niche. I wonder if we'll see two of those merge eventually.
-
Exploring Self-Hosted Email Services
Does anybody run maddy (https://github.com/foxcpp/maddy) in production or for personal matters?
-
Solutions for selfhosted internal-only email?
Yeah, that's a bummer. If you need the docs, then its here.
-
what to use for self hosting email
I've been using maddy mail server as it's quick and easy to setup for over a year now
-
Haters will say it's fake!
Both my home server and VPS have unattended upgrades with email notifications about faliures that override do not disturb on my phone. acme.sh has automatic TLS renewal configured with systemd. Maddy mail server itself runs on Docker that is also set up with systemd to automatically restart and start at reboots. When it comes to updating Maddy i just keep an eye on the release Atom feed and change the docker compose file and restart the container.
-
Modern full-featured mail server for low-maintenance self-hosted email
I wonder how does it compare to Maddy mail server: https://github.com/foxcpp/maddy
-
Cheapest way to get domain specific emails?
If you want to self hosted, I strongly recomend https://github.com/foxcpp/maddy since it's just a single binary to run.
-
merging mbox files from google takeout
If you still want to do it on your own, there is Go simple mail server - maddy where you can borrow some code or simply use it for the purpose as a IMAP server (I mentioned above, but dovecot as IMAP probably would be the best)
-
Any library to communicate with email server for managing email accounts in Go?
https://github.com/emersion has great libraries related to emails, for example go-imap. https://github.com/foxcpp/maddy is an email server written in Go that you could look into.
-
Recieveing emails with go
Check ready-to-go maddy-SMTP/IMAP server
What are some alternatives?
rqlite - The lightweight, distributed relational database built on SQLite.
docker-mailserver - Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.
pocketbase - Open Source realtime backend in 1 file
Mailu - Insular email distribution - mail server as Docker images
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
mailcow
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
Roundcube - The Roundcube Webmail suite
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
Mail-in-a-Box - Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines
Mailcow - mailcow: dockerized - 🐮 + 🐋 = 💕