Haraka
litestream
Haraka | litestream | |
---|---|---|
16 | 165 | |
4,843 | 9,997 | |
0.8% | - | |
8.4 | 7.5 | |
1 day ago | 12 days ago | |
JavaScript | Go | |
MIT License | Apache License 2.0 |
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.
Haraka
-
postale.io? Is this legit? Email hosting unlimited domains.
postale.io has an MX record that points to mail.postale.io, which resolves to an AWS IP address (probably an EC2 instance) and has Haraka listening on port 25 (if its SMTP banner can be believed)
-
Breaking Free: How I Self-Hosted My SMTP Server with Haraka. Send thousands of emails per second at the cost of pennies.
I found that Zerodha uses Haraka and Karan–their DevOps guy, mentioned it is easy-setup and performant.
-
How do you handle SMTP and service emails?
The next time this happens i'll move to a self hosted solution, like haraka or anonaddy
-
Quest for the simple SMTP Server
Haraka Like: Simple to hook into the processing pipeline Dislike: Node.js and had some issues with stability when I last tried it
-
Self-hosting email is simultaneously the hardest it's ever been (delivery) and the easiest it's ever been (setup).
Having another SMTP as a choice is cool but not as fun as something that is way more configurable (ex. Haraka), or API driven (a la Postal).
- Email Done My Way, Part 0 – The Journey
-
Looking for lightweight pop server with approved sender (full email) per user list
Look at Haraka: http://haraka.github.io/
-
Mailserver
For the record, I'm using dovecot (https://www.dovecot.org/) for IMAP and Haraka (https://haraka.github.io/) for SMTP.
-
Running a private mail server for six years, easy peasy
I run my own mail servers for small projects, though for my main email I've actually switched to ProtonMail.
It's never been easier to self host your email with projects like the following around:
- https://foxcpp.dev/maddy/
- https://github.com/albertito/chasquid
- https://github.com/haraka/haraka
Of course the usual dovecot + postfix setup is great for learning even if a bit complicated.
-
Is a 'dumb' self-hosted email server possible.
Haraka (https://haraka.github.io/) is a plugin-based mailserver written in JavaScript. I've messed with postfix before but found Haraka easier because instead of arcane configuration files I can just read, copy, and tweak a plugin to suit my needs. Policies for receiving, storing, forwarding, and ignoring mail can be arbitrarily complex.
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.
What are some alternatives?
zone-mta - 📤 Modern outbound MTA cross platform and extendable server application
rqlite - The lightweight, distributed relational database built on SQLite.
Postal - 📮 A fully featured open source mail delivery platform for incoming & outgoing e-mail
pocketbase - Open Source realtime backend in 1 file
docker-mailserver - Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
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.
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
Dovecot - Dovecot mail server
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
Exim - Exim Mail Transport Agent - source, testsuite and documentation
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines