It’s not really a full fledged web app, but I launched a WebDAV server this year:
https://hub.docker.com/r/sciactive/nephele
I use it for all sorts of things. It’s got some great features that other WebDAV servers are lacking:
- S3 support, so you can use a cloud service as the backend.
- Encryption at rest, so you can keep your data private, even when it’s stored on S3.
- File deduplication, so you can throw the same files in over and over and not use up more disk space.
- PAM authentication, so you can let system users manage their own files.
- .htpasswd authentication, so it works with other web servers.
- A simple web interface, so you can manage files in your browser (and it should work on all browsers, even absolutely ancient ones).
It’s incredibly fast compared to most other WebDAV servers, too.
I use it to manage my Jellyfin libraries, as a personal cloud storage, and as a deduplicating backup server. It works well through a reverse proxy too, so I have multiple instances running on my server with different configs.
There’s also a desktop app that uses the same server under the hood to let you transfer and manage files across your network:
Why this versus NC or baikal
Did you read my post?
It’s faster and has a different feature set. Also it’s written in Node.js, not PHP, so I can integrate it into my Node.js apps.
Neither of the servers you mentioned can work on a flat file system folder, so managing my Jellyfin media wouldn’t even be possible with either of them.
Neither supports file deduplication, encryption at rest, PAM authentication, or .htpasswd authentication.
Both require a database and can only be managed through their web interfaces.
Both of their web interfaces require modern browsers, so wouldn’t be supported on something like a terminal based browser.
It’s faster and has a different feature set. Also it’s written in Node.js, not PHP, so I can integrate it into my Node.js apps.
Neither of the servers you mentioned can work on a flat file system folder, so managing my Jellyfin media wouldn’t even be possible with either of them.
Neither supports file deduplication, encryption at rest, PAM authentication, or .htpasswd authentication.
Both require a database and can only be managed through their web interfaces.
Both of their web interfaces require modern browsers, so wouldn’t be supported on something like a terminal based browser.
Thanks! That’s sounds great.
Working on my better Hoarder alternative. Goal: maybe 2025.
Thoughts on linkding?
I haven’t been able to try Linkding on any of my servers yet, as neither OpenBSD nor OmniOS are supported. I would probably like it if it did.
Best of luck. What do you find lacking so far?
- There is no obvious way to install Hoarder on an unsupported platform. My servers run OpenBSD and OmniOS. Both of them don’t even have any Docker support. (Which is not something I’d absolutely need, to be honest.)
- Hoarder runs on Node.js. I will use Lisp (edit: or probably not, but Rust). Node.js is a dependency hell.
- Hoarder does not really encourage manual and/or regex-based tagging, it strongly suggests relying on “artificial intelligence”. As I am rather disappointed by what “artificial intelligence” is currently able to do, I’d prefer to default to the old approach.
Of course, all of this is just a personal preference.
Have you looked at sandstorm? Or used it?
It’s one of my favorite stacks, and I’m curious to hear your thoughts.
It’s more or less abandoned, isn’t it? Or has the community support picked up? The team left the company for cloudflare years ago and I would dare to say the tech stack itself is deprecated once docker became so widespread.
