Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)M
Posts
4
Comments
142
Joined
2 yr. ago

  • I'm currently using an i5 9500 and it runs good here too.

    Note for OP though: If you don't need/want transcoding it'd be way cheaper to get an equivalent AMD CPU just because motherboards are hilariously expensive for an obsolete platform.

  • I used a RaspberryPi 4B for about 3 years. I connected storage over USB-3 to a pair of SATA SSDs. It handled everything pretty much flawlessly for two users and half a dozen devices. We even had multiple users on Plex. dietpi was brilliant for my first home server :).

    Initial uploads may be slow depending on your storage layout but in my experience the requirements are super low.

  • Good point!

  • I have definitely considered Fabric Server. It might give me opportunities for some smaller mods later.

  • In terms of pricing, I find Hetzner is best for under 1TB, Backblaze for over 1TB. Both have great documentation for setting up any number of backup methods (SFTP, SSH, Rsync, Rclone, Borg, etc).

    Rsync, Rclone, and Borg are all good options and some may be built into your choice of OS if you use a dedicated NAS system. Choose whatever is easiest for you.

    The backups are gonna be encrypted in transit regardless of method, and Im pretty sure most backup providers encrypt data on their servers so you dont have to manage that I dont think.

    When you commit to backups, IMO you should do them daily - Most backup clients have options for "sync" options which will ignore unchanged files and only upload changes, so a daily backup is not only more up-to-date but also more efficient once the first backup completes.

  • Imagine!

    RISC-V CPU backed by RISC-V motherboard controllers, DRAM controllers, storage controllers etc., and a RISC-V GPGPU for gaming and hardware acceleration.

    It feels like that's a million miles away but we already have working designs for every single proprietary chip used across the average computer!

  • It's too late for me now coz I didnt do my research and ive already migrated over, but good god ever loving fuck was the AIO container the hardest of all my services to set up.

    Firstly, it throws a fit if you don't set up the filesystem specifically for php and the postgres db as if it were bare metal. Idk how or why every other container I use can deal with UID 568 but Nextcloud demands www-data and netdata users.

    When that's done, you realise it won't run background tasks because it expects cron to be set up. You have to set a cronjob that enters the container to run the cron, all to avoid the "recommended" approach of using a second nextcloud instance just to run background tasks.

    And finally, and maybe this is just a fault of TrueNAS' setup wizard but, I still had to enter the container shell to set up a bunch of basic settings like phone region. come on.

    Straight up worse than installing it bare metal

  • Thats a shame. I use Hetzner for my offsite backups because they're so damn cheap for my usecase.

  • I've kept a raspberry pi 4b that's given a mild OC to 1900Mhz in my boiler cupboard for a year and all its needed to keep it below 50 is:

    1. a tiny metal heatsink
    2. a 5w usb fan blowing already-warm air sorta towards it
  • I'm quite new to docker for NAS stuff - how many pulls would the average person do? like, i don't think i even have 10 containers 🤨

  • 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.

  • Small note, the *arr stack (at least when running in docker) will prefer you mount qbittorrent's download folder to /config/Downloads (case sensitive). otherwise it whines about paths in the health menu

  • 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

  • People have really weird usernames sometimes

  • True, but there are other benefits too. Bots can't crawl through your likes for example. Maybe you want a feature on lemmy or mastodon or whatever with anonymous polling? (ik masto has polls but for sake of argument) Maybe you're implementing anonymous polling into an app for a trade union that needs total anonymity even from admins? It's not totally unusual!

    IMO it makes sense to do this at a platform level just because there's a unified implementation of obfuscation across all the fediverse for any platforms that want to use, rather than a bunch of unique solutions that would be duplicated effort.

  • 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.

  • If that were to happen, broadcom would get away with x86 licensing rights, correct? Not sure how intel graphics would fit into that deal.