this post was submitted on 30 May 2024
24 points (92.9% liked)

Selfhosted

40041 readers
748 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I moved off a Synology NAS to a self-managed machine and one thing I still struggle to replace is something like a synology drive. Here are my requirements:

  • server side store data in a plain FS (I want transparency)
  • client side (windows), it must support VFS (download files when needed, support offloading of large files)
  • having snapshots of data is a must

I have a 40gbit uplink to my desktop, so if everything else fails I’ll just use samba with zfs snapshots exposed to VSS, but we’re talking some large files still (think several hundreds of MBs) and I’m not sure Blender will be happy working off a network disk.

I’ve been pointed to next/own-cloud previously, but they don’t seem to cover my use case, I think. Should I actually try one of those? I browsed around owncloud's storage bit (which is written in go), and it seems mostly fitting, but I’ve been told I should steer away from ownCloud towards nextCloud.

you are viewing a single comment's thread
view the rest of the comments
[–] sloppy_diffuser@sh.itjust.works 2 points 5 months ago

I haven't tested in Windows, but this is my setup Linux to Linux using rclone which the docs say works with Windows.

Server

  • LUKS
  • LVM
  • Volgroup with a mishmash of drives in a mirror configuration
  • Cache volume with SSD
  • BTRFS /w Snapshots (or ZFS or any other snapshotting FS)
  • (optional) Rclone local "remote" with Crypt if you want runtime encryption at rest and the ability to decrypt files on the server. You can skip this and do client side only if you don't want the decryption key on the server.
  • SFTP (or any other self-hosted protocol from https://rclone.org/docs/)

Client

  • Rclone Config /w SFTP (or chosen protocol)
  • (optional) Rclone Config /w Crypt
  • Rclone mount with VFS.

I use this setup for my local files and a similar setup to my Backblaze B2 off site backups.

The VFS implementation has been pretty good. You can also manually sync. Their bisync I don't fully trust though.

I can access everything through android using https://github.com/newhinton/Round-Sync. Not great for photos though as thumbnails weren't loading without pulling the whole file last I tested a year ago.