- cross-posted to:
- technology@beehaw.org
- cross-posted to:
- technology@beehaw.org
I made a video about copyparty, the selfhosted fileserver I’ve been making for the past 5 years.
The main focus of the video is the features, but it also touches upon configuration. Was hoping it would be easier to follow than the readme on github… not sure how well that went, but hey :D
This video is also available to watch on the copyparty demo server, as a high-quality AV1 file and a lower-quality h264.
the intention with that statement was that seafile, by default, places all the files inside its own proprietary file container thing, where the files are not easily accessible from the server’s actual filesystem, using regular linux utilities. My knowledge of seafile is really minimal, so this could be wrong – in which case I’ll fix that right away! or, at the very least, try to clarify what I meant to avoid this confusion.
in case you happen to know – are you aware if it’s possible to use Seafile while having it just place all the files and folders on the disk like any other program would?
@tripflag @disobey2623 Your statement is correct; the way seafile stores files is in blocks (for de-duplication, apparently).
They offer a fuse extension that allows you to view stuff like a normal filesystem, though I’ve never tried it: https://manual.seafile.com/latest/extension/fuse/