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/)TO
Posts
5
Comments
133
Joined
2 yr. ago

  • Admittedly I'm not very knowledgeable about different pruning ways. I'm friends with a gardener and usually follow their recommendations. We have one very old and large apple tree that we would like to keep alive as long as possible (fruit bearing or not) and some new trees where we don't cut too much except for inwards-growing water sprouts. Generally prioritizing harvest and tree resilience, plus some extras with the old tree.

  • I also planned to do the same (bare nginx instead of NPM but otherwise the same). Did you just remove the nginx container from docker compose and use the same arguments in NPM or do you double-reverseproxy or something else?

  • I mean every other week. I wasn't aware of the other interpretation, but I think in combination with "The Sunday thread" it's unambiguous?

    I have never heard fortnightly, but then I'm not a native speaker. Is that commonly used?

  • I would run Debian from a stick and install Proxmox with the installer and not on top of Debian unless you have to. While the latter works, I found some settings around network interfaces to differ between the installation methods which caused me problems here and there.

  • Personally I'm mostly involved with my homelab migration so there's not too much on the selfhosting page except os updates. I set up meshmini earlier to access my thin clients via vPro/AMT but I need to configure the clients before being able to actually using meshmini. Once I'm done with that I'll finally be able to set up Lemmy and Pine pods.

    My selfhosted stuff currently works fine without me doing much which feels good and lets me focus on hardware stuff currently.

  • Selfhosted @lemmy.world

    What's up, selfhosters? - The Sunday thread

  • Not answering every single point but generally: I'd set up proxmox, test everything, make notes, reach a state/config that you like, and then start over doing it "properly" from start.

    Personally: ZFS yes, quemu/lxc depends on use case

    I shy away from running all services as Docker on the same machine for backup/restore purposes and rather have VMs per service. Is there anything wrong with this approach?

    No, but you'll have much more overhead. I have a VM that hosts all Docker deployments which don't need much disk space (most of them)

  • Use whatever you have and test different setups. I would start by installing Proxmox and setup ZFS on some drive that not the boot partition. For just checking it out with some lightweight VMs and containers any CPU that's not 20 years old will suffice, the more RAM the better. Play with VMs, backups etc in small scale. You can use your old external USB HDD, etc, just to figure out things like ZFS.

    Don't buy anything before getting some experience and having some kind of plan.

  • Selfhosted @lemmy.world

    What's up, selfhosters? - Sunday thread

    Selfhosted @lemmy.world

    Ghost blog adding activitypub

    Selfhosted @lemmy.world

    What's up? - Sunday weekly

    Selfhosted @lemmy.world

    Kiteworks acquires ownCloud & Dracoon - Nextcloud