www.keycloak.org - auth mostly for outline
www.getoutline.com - my personal "notion"
nginxproxymanager.com - to proxy things
Wireguard - remote access and interconnection between zones
cockpit-project.org - to manage VMS
github.com/coder/code-server - To remote develop
2x of docs.paperless-ngx.com/ (one for me and one for my partner) - I scan and destroy most of the letters I get.
snibox.github.io/ - my terminal companion
pi-hole (together with wireguard I don't have ads on my devices)
uptime.kuma.pet - to be sure that things are online
mailcow.email/ - for non priority domains
docs.postalserver.io/ - mail server for apps and services
At home (small 6w nic with):
HomeAssistant - To control home lights
Cups - share printers
Wireguard - (connected to the cloud)
Even though I sold mailcow and stopped working on it in the past months, it warms my heart SO MUCH to see people using it. :) Really, thank you.
I have some ideas for a proper successor which would be much more scaleable, modern, flexible and would be more focused to use existing transports for piggybacking mail. A fully and safely encrypted mail storage as well as a cool interface to invite for encrypted sessions etc.
Smtpd and imapd using modern Python modules.
—
Providers found out it was easier to block private senders instead of developing good filtering mechanisms. I kind of understand this decision, but spammers simply abuse services like Sendgrid or create spam accounts on MS.
So… nothing really changed in regards of spam. We just lose actually *wanted* mails or have to look into the Junk folders more often, all while newsletters get on the priority lane.
That makes me unsure about developing anything in this regard. :(
Hi Andrè! I just wanted to thank you for mailcow! We used it a few years ago at my previous job to getting a new domain up & running and got a porfessional, best-practices-configured email server in no time. Great experience also for day 2 operations! Nothing like the other mail solutions available at that time.
To the new owners: I googled mailcow, got to the web site and found nothing to explain what it is, not even in the docs. Eventually I noticed the "People also ask" section in the Google results page:
> What is Mailcow?
> fully managed by Elestio. Mailcow is a Docker-based email server, based on Dovecot, Postfix and other open-source software, that provides a modern web UI for administration.
> When I did the setup last year paperless-ngx look like the most maintained.
Just FYI, none of those were hostile forks, but in both the community taking over after the former maintainers abandoned the project. NGX is indeed the active version.
I used paperless for a while but ended up just saving pdfs to directories instead. I can find what I need without fancy OCR features by organizing and naming files sensibly. And I am fairly certain this will still work in 40 years, while paperless, or even Linux, might no longer exist.
That was sort of the approach I had been planning on going for (manual scanning and putting it in directories that get cloud backed up). I have a pretty good scanner app on my phone, and so just scanning after opening the mail for some important document or invoice, uploading to the document storage, and then shredding seemed to be pretty low fanfare.
In the end, paperless also stores the original pdfs in a directory. You get some more goodies from it, like automatic OCR and a web interface, but your baselines is also included.
Why not do both? Use rsync to do a one way sync by keeping a filter list to the paperless consume directory so whenever you drop any new documents to your original folder structures, it copies THAT to the consume and paperless consumes it?
I can recommend paperless. I am running it locally in a Docker container and sync database/files with iCloud (so they are backed up). I've been thinking about putting them on the actual web to access them anywhere, but so far having paperless "just" on my computer was enough.
Thanks for sharing this list! I wasn't aware of nginxproxymanager. This is something I've been doing semi manually for years. It looks like it'll slot right in and save me some work
I pay $20/yr for their service it’s so good, and I can turn on/off quickly per-device when I need normal dns to work, instead of having to ssh and tweak pi-hole or whatever across the whole network
The biggest curse of the Raspberry Pi is a whole heap of stuff that has gone from “needs a UNIX server” to “but surely that requires an underpowered UNIX server with a very specific distribution of Linux”.