Because this is r/selfhosted. :-)
adamshand
joined 1 year ago
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.
Assuming you already have a shared calendar system, just setup a shared calendar for whatever resources you need to schedule.
I don't understand this sub sometimes. You are very right.
This sub's aversion to hosting email (and now DNS) is bizarre.
As another option why not docker swarm? I think it will do what you need and is much simpler than k8s.
I’ve been using caprover and really liking how simple and reliable it’s been. In the process of going from a single node to a swarm, still researching / experimenting but liking it so far!
I use a todo app for this. I have a Read/Watch list and just add things there.
I like this because it's super fast/easy to add something, I can sync todos to all my devices via CalDAV, and I am regularly reminded about them when I use my todo list. :-)
KVM (Kernel-based virtual machine) is just a specific technology to provide a VPS (virtual private server).
There's no reason for you to care about the tech stack at this point, just get a VPS that is geographically close to you and is reasonably priced.
I like the $5 / month Vultr VPS, but there are other cheaper options.
There are many, many prebuilt open source projects.
You might find starting with something CasaOS, Unraid, or TrueNAS an easier way to start. I haven't used any of them, others may have better suggestions on ways to start on a VPS.
Rsync is great, but unless you are using a system on top of rsync (eg. rsync-backup) it only gives you a single copy which isn't the best option for backups.
For example, you accidentally change a file but by the time you notice the version you want has been overwritten.
There’s nothing inherently insecure about exposing a service to the internet. But it does create an attack surface.
A firewall or proxy (Cloudflare, Nginx etc) allows you to restrict access via ip address or authentication, but if there’s a bug in your service it can still be exploited.
The good news about a service you write is that there are no ready built tools to exploit it. The bad news is that there are almost certainly more bugs.
So it really comes down to what your ap has access to (is it jailed or restricted in someway), is it read only or does it allow modifying file in the system? How confident are you with your code? If someone starts bashing in it, will you be alerted? Is it did get a coloured how serious would that be? There is no “right” answer, is a risk assessment you have to make based on your situation.
The enshitification begins …