I welcome PRs to add additional sending providers - it wouldn't be onerous.
Of course, tech bros don't want you to do it, as it reduces their vendor lock-in.
Really I was just concerned about configuration overload from too many options. Seems like SMTP is worth splitting out, though.
Solution is:
* SMTP by default
* if you want, some setup examples of using third-party mail services using their SMTP endpoint (most offer one)
Again you don't have to, it's an open-source project and you owe nothing to anyone. But if you fancy doing it, this is the way to go and will save headaches later.
Who's the relatively better provider now?
Edit: A useful article about IP Warm up https://blog.healthchecks.io/2023/08/notes-on-self-hosted-tr...
SES is terrible in the past but now it is at least on-par if not better than postmark.
Only issue with SES is setup can be tedious.
May I ask what were your biggest hurdles building the project and what's the most requested feature from your users?
I myself have been building similar project called `Open Payment Host`[1] for couple of years now, but its focused on payments. Say a self-hosted alternative for Gumroad, Buy Me a Coffee, Ko-fi etc.
Indeed it is so performance sensitive, that it has blocked my region. Would it not be better to get a static site generator from a standard Markdown posts, and thus assure it is both performant and accessible?
My hosting setup is . . peculiar: https://www.contraption.co/a-mini-data-center/
Please avoid comments like this on HN, and make an effort to observe the guidelines.
Github, Airbnb, Shopify, Stripe, Basecamp, Instacart, Zendesk, Square, and others seem to be staying online, too.
I've written more about my Ruby opinions here: https://www.contraption.co/rails-versus-nextjs/
(Discussed on HN here: https://news.ycombinator.com/item?id=43130546 )
Ruby is effectively Rails. Something about this has always bothered me because I don't like ruby and it gets SOO much praise from users. Which all almost universally happen to be using Rails. I've never used rails so I could not say why authoritatively. I did find someone recently on here that talked about it and mentioned that Rails is steeped in "magic". That it is unbeatable for a single person founder to create a project of any size. The problem is all that "magic" becomes a huge point of contention/confusion/friction when non rails zealots get involved, which is basically everyone.
Or to be more to the point Ruby and rails has a very specific use case and that use case has nothing to do with the application you are building rather the type and size of Team you are assembling.
To me its just a more obscure Python with a much smaller more enthusiastic user base.
Rails and Ruby on the other hand offers one of the best ecosystems and a lot of stability