aerc VS Coolify

You have some points, for some I do think it isn't as bad as you write. FWIW, some comments inline. > - You can't subscribe to a single PR/bug/feature-request thread. Subscription to the mailing list is all-or-nothing. And no, setting up email filters is not a reasonable solution. You can use tools like public-inbox or lei, the former is hosted for bigger projects on https://lore.kernel.org/ If you're interested,... - Source: Hacker News / 7 months ago

> Another problem is how badly email threading is displayed in these clients. Email UI is still abysmal. Fair point. However, given that the current alternative is "use another service entirely (e.g. GitHub)", I think it would be fair to assume that devs could choose a good e-mail client and learn how to format such e-mails correctly. It works for Linux, for instance. I started using Aerc, and I love it:... - Source: Hacker News / 9 months ago

For fans of Mutt/NeoMutt looking to try something new, I've been getting a lot of mileage out of Aerc[1] and can recommend it as a somewhat more approachable alternative for the Mutt-curious. [1] https://aerc-mail.org/. - Source: Hacker News / over 1 year ago

Try aerc, I recently set it up and it was really easy to do. The only tricky part was making it so my password is read from the KDE wallet instead of being stored as plain text in the config file. Source: over 1 year ago

I'm not sure how much longer, but at least for me aerc still works with Outlook e-mails. Source: over 1 year ago

Solutions like pocketbase and coolify come close to solving these problems. However, I wouldn't choose either as I fear architecture lock-in as much as vendor lock-in. Especially in the case of pocketbase, I may be forced to rewrite my application if it were to scale overnight. - Source: dev.to / 4 days ago

This is my first quick try deploying SvelteKit with the open source software Coolify by Andras Bacsai. - Source: dev.to / 18 days ago

With a serverful approach, you can avoid these drawbacks, and the main challenge lies in selecting the platform that aligns with your requirements. Options may include AWS, Render, DigitalOcean, and others. While VPS is also an option, it's generally not recommended due to the significant setup and maintenance overhead involved (logging, monitoring, CI/CD pipelines, etc.). However, you can make your life easier by... - Source: dev.to / about 1 month ago

Heroku and similar providers can simplify the server management issues, but you can use something much better that can combine both cost efficiency and ease of deployment—Coolify:. - Source: dev.to / about 2 months ago

> VPSs being “easy to manage” is a strong option full of assumptions. There are definitely many footguns with managing a VPS but I think the threshold to get vaguely competent with a VPS is not really that far off with getting familiar with the average cloud platform - which comes with its own dangers, like the near-total inability to put an upward cap on fees that that person found out with Netlify recently.... - Source: Hacker News / 3 months ago