There's no technical problem with running a mail server on the same server as websites. The only concern is simply that web applications are much more likely to have bugs and get hacked than your mail server. If a web app does get hacked, all of your mail is potentially compromised. If you don't care about that, I'd say ... go for it.
Sadly, I believe web push notifications still go through a centralised server provided by the browser developer.
I thought limits only worked in swarms?
I just checked the docs and didn't see anything about ntfy accepting smtp? This would be useful, what am I missing?
You have climbed mountains and gained skills. Congratulations my friend, now bask in the soothing waters.
One thing that threw me in the beginning was that the docs didn't show examples in context. As an example, if you look at the basicauth docs it shows:
basicauth /secret/* {
Bob $2a$14$Zkx19XLiW6VYouLHR5NmfOFU0z2GTNmpkT/5qqR7hx4IjWJPDhjvG
}...
}
Where can I use this? Globally? In the top-level of the virtualhost definition? If I'm reverse proxying, do I put it inside the reverse_proxy stanza? I used Apache for years and the docs always stated what context directives could be used in, eg.
https://httpd.apache.org/docs/2.4/mod/core.html#acceptpathinfo
I used Apache for many years. It’s great! But Caddy is simpler, easier and lighter weight.
Because this is r/selfhosted. :-)
Nice!
I used Apache's webdav server for years for this kind of thing.
https://httpd.apache.org/docs/2.4/mod/mod_dav.html
Caddy also has webdav support:
I switched from Traefik to Caddy a few years ago and have no ragrets. The only complaints I have about Caddy:
- It doesn't support configuring virtual hosts automatically via docker labelsl (like Traefik).
- Many features (like DNS auth for certs) require compiling Caddy. Which is easy but annoying.
adamshand
0 post score0 comment score
r/lostredditors