dufs VS watchtower

Sounds helpful if you're using Apache. I use dufs (https://github.com/sigoden/dufs) as a lightweight file server.

I'm with you on wishing WebDAV continued its rollout. These days there are great low-drama server-side deployments like https://github.com/sigoden/dufs. It's run relative too - you could habe multiple dufs processes serving up different directories in different ways. But for WebDAV, you can't simply mount that on the client side for every OS that's equally low configutaion. For that reason, I really like sshfs as it can be initiated from the client-side without a lot of config (just a mkdir of the mapped dir), and it's OK most time despite it's lack of speed and multi-day uptime. I'm on a chromebook now and it turns out that Samba is the easiest client-side tech to use for remote file systems. DAv should've been uniquitous.

WebDAV: https://github.com/sigoden/dufs - has an easy way of launching, and on the releases tab downloads for multiple CPUs/OSs. The rust exe can just be executed from the cli without installation via package managers (wget and tar xf) are all you need.

I use sigoden/dufs. Very simple file browser that doubles as a basic http server. Supports upload, download and basic file manipulation. I feel it's utterly underrated.

So sorry. It only has one f. https://github.com/sigoden/dufs

dufs miniserve

My solution for public media distribution is Caddy¹ on Scaleway Stardust². 10gb of storage isn't really enough (someday I will write I/O for the 75gb of free object storage), but offers unmetered 100mbps data transfer for $3/month. I setup a proxy through Caddy to dufs³ to upload files.

Anything worth keeping goes on an external HD, buy a bigger one each year and make another copy. I also upload all irreplaceable video to Youtube as private videos; I recently went through and granted a few people access to the ones they wanted to see.

¹https://caddyserver.com

²https://www.scaleway.com/en/stardust-instances

³https://github.com/sigoden/dufs

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!