"There are two editors in case you hate one of them"

You crack me up !!!

sure! my implementation is really basic, just the stuff that's needed to make the clients i've tested happy, so there's probably still clients that won't be able to connect (And i'll fix those as soon as I hear about them!)

httpcli.py is the http methods handler, and the webdav-specific handlers are all next to eachother, propfind // proppatch // lock // unlock // mkcol // and there's also put for the uploads, but that's not entirely webdav-specific, just webdav-aware.

Congrats on the cat box cleaning!

SFTP is not currently on the roadmap, but it's not entirely implausible.

FTPS is supported, but it requires an optional dependency to be installed (pyopenssl), so it's not available in the Windows EXE. And I just realized that the dependency is currently not present inside the docker images either, so I'll get that fixed right away.

BTRFS and ZFS support real deduplication via copy on write, and would eliminate all current disadvantages of symlink and hardlink deduplication. It just works.

yeah that's a good point, I'll add an option to take advantage of this if you know you're running on a filesystem where that works as intended.

Why have it be one huge python source file?

oh don't worry, it's all separate files during development -- there's a build-stage which bundles everything up into a single file for distribution. But thanks for the concern :D

Just a remark from someone who runs ZFS since the beginning. Many people don't like the deduplication feature because of its memory footprint.

It's also nice to have this feature without relying on a certain filesystem.

so uhh, sorry for the late response to this -- was going to reply much earlier, but then suddenly it became more timely than ever...

the good news is, I'm fairly confident in how it handles the filesystem and permissions, preventing unauthorized access to files.

but the part I'm a bit less sure about is sanitizing user data; the kind of vulnerabilities where someone uploads a malicious file and bad stuff happens if you then open that file in a certain way, or someone sends you a malicious link and trick you into clicking it -- in other words, the kind of vulnerabilities which require the attacker to have a certain level of access already, or that requires tricking you into doing something.

...and with version 1.18.5 released just now, we got a prime example of exactly one of those. Really unfortunate timing, but it's a blessing to have so many new and curious eyes on it to spot these sooner rather than later. It is what it is.

Agreed.

Yup, I tried to run the docker image with the suggested docker command and it errored out for lack of a config file (though it did offer a fix in the logs for mounting the current directory as read/write)

The docker compose file worked great for me.

it's such an impressive project! Amazing what they've accomplished in so little time, and so important too -- we need as many options as we can get.

That's a neat idea -- I've heard that a lot of stuff uses the subsonic API under the hood, so I'll see what it would take to become compatible with that. At first glance it looks like I'd have to mine and index way more information about audio files, but could still be doable :>

Did you hear anything about translations? I’d also be down to help translate.

Just curious, why did you replace nextcloud? I'm looking into transitioning from my current file server, and I've mostly heard only good things and not NextCloud.

I haven't even tried it yet, but just from the video you can tell it's going to be insanely good. I'm so impressed.

It's the first bit of software I've seen in a long time where I took one look and immediately thought "Fuck me, I need that!"

I use Unraid for my NAS server and just on the off-chance I checked the Unraid community 'app store' and someone's already created a Docker definition for it, published just today! The hype is real

I'll be giving this a shot

thanks for the vote, I hear ya :>

Thanks a lot for the kind words! ready to answer questions if you hit any bumps :>

No worries, good question :>

The problem with bidirectional filesync is that it's an absolutely massive can of worms, very easy to mess up, and the consequences of messing up are usually the worst kind (loss of data). There's an insane amount of edgecases to keep in mind, and you need to get every edgecase right every single time, otherwise you might wipe someone's vacation photos, or suddenly downgrade someone's keepass database to an older version... And stuff like syncing multiple devices to the same server makes it balloon further.

I've started becoming more confident in copyparty's filesystem-index database, but it's still just a hint/guideline, with the filesystem being the only source of truth -- it's still not something I'd trust with tracking sync-state against one or more clients.

The bigger guys who offer bidirectional sync (nextcloud, syncthing, etc.) have spent years perfecting their logic, so I'd like to leave this in their capable hands.

That "functional but charming" UI reminds me of audiobookshelf with the soundleaf app - same vibe where it dosn't look fancy but gets the job done better than most polished alternatives!

There is a link to a live demo pretty close to the top.

At this rate might be faster to read code than a read me. Or convert to a wiki style if this much details are really needed.

Thanks for the correction; confirmed that Nextcloud now does chunked uploading (with the web-client too). Fixed :>

Good luck, and let me know if you hit any issues o/

Oh yea, copyparty could do that. I might just do that too. My issue is more how do I grant them access to my network to get the thing tough? I currently use wireguard profiles and lock down where they can reach with rules and shit on a firewalla on a per account basis but that’s really complex and inelegant. It works and would working copypasta, but I kind of wish there was a simple webUI where I could define what a WireGuard user should be able to reach on my network with simple checkboxes by rules I have created over time. Probably wouldn’t tie into firewalla nicely though it could be more likely with OPNsense.

Hmm. Surely someone must have thought of that already. It would make adopting things like copypasta much simpler and less risky.

I think Copyparty would be great for that purpose. The only thing you're missing is a way to expose it to the internet, such as a public IP or some tunnel

"It's janky. It's charming. It works. It's Copyparty." ®

I have a hunch that the true answer, to be honest, is "no" -- at least with the current UI as it is. I've come to terms with not being the best at making intuitive user interfaces, so I went all-in on making it poweruser-friendly and efficiency instead.

Yeah, there's the android app for sending files to the server, and it'll always send files to the same folder, so that part should be pretty solid. But actually grabbing files from the server, perhaps not so much. Not sure I'd risk it, but I'll leave the decision to you hehe

I'm not aware of any user-friendly android/iOS apps for connecting to a webdav / ftps / sftp server, but if those exist, then that would probably have been a good option!

If all you need is basic remote file storage such as a samba server, and especially if you need samba in particular, then your current solution is probably a better fit for you.

Copyparty's main selling points is the large number of features in one package, and being pretty good at receiving file uploads (usually faster than other alternatives), but it does not have good samba support. Instead of samba, copyparty has WebDAV support, so you can still connect to it from your file manager -- but the performance will be different; depending on your access pattern and the type of files, it could be faster or slower than samba.

I would add PairDrop to your list to have bookmarked. It's completely web-based so no download required and thus fully cross-platform. It also works across different networks (i.e. over the internet) by pairing devices or creating a room. Basically Apple AirDrop, but universal and on steroids.

For such operations we use LocalSend.

man... that's really unexpected, I went with h264+mp3 which should be the most conservative / broadly-supported combination you could possibly use, yet still (ﾉ ﾟヮﾟ)ﾉ ~┻━┻

what webbrowser / device / player are you using?