orhtej2@eviltoast.org to Programmer Humor@programming.devEnglish · 2 days agoNever!eviltoast.orgimagemessage-square115linkfedilinkarrow-up11.29Karrow-down13
arrow-up11.29Karrow-down1imageNever!eviltoast.orgorhtej2@eviltoast.org to Programmer Humor@programming.devEnglish · 2 days agomessage-square115linkfedilink
minus-squareXeno@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·12 hours agoGet started with a Linux server and then I’d go with something like Nextcloud in a Docker container. Then do reverse proxy, nginx on the host is very easy. You can get and update SSL certs with certbot (Let’s Encrypt).
minus-squareCrayonDevourer@lemmy.worldlinkfedilinkarrow-up2·7 hours agoJust do Caddy instead of nginx/cerbot all that garbage. Caddy just simply handles it all for you: Subdomains, wildcard certs, authentication, ssl My whole caddy config file is like 6 lines; something like @mydomain.com { ipaddress:port path:/ } And you can do all sorts of plugins that make it compatible with fail2ban, etc. I hear Traefik is pretty easy to set up too.
Get started with a Linux server and then I’d go with something like Nextcloud in a Docker container. Then do reverse proxy, nginx on the host is very easy. You can get and update SSL certs with certbot (Let’s Encrypt).
Just do Caddy instead of nginx/cerbot all that garbage. Caddy just simply handles it all for you: Subdomains, wildcard certs, authentication, ssl
My whole caddy config file is like 6 lines; something like
@mydomain.com {ipaddress:portpath:/}And you can do all sorts of plugins that make it compatible with fail2ban, etc.
I hear Traefik is pretty easy to set up too.