• 2 Posts
  • 104 Comments
Joined 8 months ago
cake
Cake day: August 22nd, 2024

help-circle


  • There’s a bunch of technical debt passed off as features, too. Like, Nextcloud runs background tasks as a cron job which is something I’ve never seen with other hosted services. It’s probably a holdover from before containerised applications were ubiquitous but honestly it comes off as jank.

    Also, I wonder if there would be an argument for a Nextcloud fork that doubled down on PHP by utilising something like Laravel to put all the rendering on the server side. Right now it uses VueJS which is fine, but PHP is really best suited for server side rendering that you just can’t leverage when using a front end framework in JavaScript.






  • MergerFS and SnapRAID could be good for you. It’s not immediate parity like with ZFS RAID (You run a regular cronjob to calculate RAID parity) but it supports mismatched drive sizes, expansion of the pool at any time, and some other features that should be good for a media server where live parity isn’t critical.

    Proxmox and TrueNAS are nice because they help manage ZFS and other remote management within a nice UI but really you can just use Debian with SSH and do the same stuff. DietPi has a few nice utilities on top of Debian (DDNS manager and CLI fstab utilities, for example)but not super necessary.

    Personally I use TrueNAS but I also used DietPi/Debian for years and both have benefits and it really matters what your workflow is. OMV supports everything you want too (incouding SnapRAID) but takes extra setup which put me off.

    Docker or LXC containers won’t hurt your performance btw. There’s supposedly some tiny overhead but both are designed to use the basic Linux system as much as possible: they’re way faster than on WSL. For hardware acceleration it’ll be deferred to the GPU for most things and there’s lots of documentation to set it up. The best thing about docker is that every application is kept separate to eachother - updates can be done incrementally and rollbacks are possible too!



  • You may have to use port forwarding or a reverse proxy but the end result is functionally identical to plex. IMO the server detection feature of Plex is overengineered for what it is, and I just sit it behind my reverse proxy and connect to it that way.

    As for music and apps yeah Plex is pretty nice, but even for audio you could use other services if Jellyfin didn’t fit your needs like Navidrome





  • I don’t have much issue with email as a technology. It does what it needs to do, and does it well. The client side software is what hasn’t budged in years - Search barely works, files and attachments are cumbersome, and spam is still rampant.

    It would be much cheaper and easier if users weren’t centralised under a few big providers that prefer to bar any and all access to said users if you’re self hosting, making it almost mandatory to use a private service.



  • Yeah it’s pretty much seamless. You just spin them up bare metal or docker (both are fine honestly) and follow any old tutorial for setup.

    If using docker, ensure you mount the qbittorrent’s download folder to /config/Downloads with a capital D or you’ll get a warning about paths being set up wrong.

    Also, I assume this isn’t really an issue for you unless you mess with the downloads after the fact, but *arrs expect the torrented media inside a folder with the title of the media on it. It picks through torrent naming conventions fine, but when I migrated some movies yesterday I noticed it wouldnt pick up any video files that weren’t inside a directory.




  • My current plan once new migration is completed:

    Primary pool - 1x ZFS (couldn’t afford redundancy but no different to my RPI server). My goal is to get a few more drives and set up a RAIDZ1/2.

    Weekly backup of critical data (eg. nextcloud) from primary pool to a secondary pool. Goal here is to get a mirror but will only be one drive for now.

    Weekly upload of secondary pool to hetzner storage box via rsync.


    Current server

    1x backup to secondary drive (rpi) 1x backup to hetzner storage box via rsync



  • quicksync should let the i3 handle jellyfin just fine if you’re not going beyond 1080p for a couple of concurrent users. Especially if you configure the Nice values to prefer jellyfin over immich.

    I’m not aware of the platform for the n300 because it might be worth the initial setup, and have some room to upgrade the CPU later if it causes trouble.

    If OP is going for multiple systems, I’d definitely agree on making one of them a pure NAS and let a more upgradable system run the chunky stuff.