63
Mini pc arriving tomorrow (lemmy.dbzer0.com)

Greetings, so I final got wife permission to buy a pi zero 2 and a beeline 12s pro (n100) arriving tomorrow. I already have a nas drive for my media.

Question is what is the average setup and guides for this?

Of course I will be scouring this and other communities for info but the immediate items I want to fix are my plex/jellyfin server, setup RetroArch or equivalent gaming, then of course arr servers. But I would like to also get into reverse proxy and searxng, next cloud and pihole.

Any tips on how to make this beautiful?

OS recommendations? I currently run manjaro on my daily, but would think a kubuntu or kde fedora/debian spin might be better for these items.

Guides you can point me to? Suggestions for more or better options? There are plenty of answers in this community and I will look at what’s posted but any assistance is appreciated.

Thank you in advance.

I’m excited to start plying with the simple things

you are viewing a single comment's thread
view the rest of the comments
[-] Dran_Arcana@lemmy.world 12 points 1 day ago

Not sure if many people do what I do, but instead of taking notes I make commented functions in bash. My philosophy is: If I can't automate it; I don't understand it. After a while you build enough automation to build your workstations, your servers, all of your vms and containers, your workflows, etc, and can automate duplicating / redeploying them whenever required. One tarball and like 6 commands and I can build my entire home + homelab.

[-] Siathes@lemmy.dbzer0.com 3 points 14 hours ago

Can you elaborate on this a little more, sounds interesting and reinforcing?!

[-] Dran_Arcana@lemmy.world 1 points 7 hours ago

Sure. I have an r630 that is configured as an NFS server and a docker host called vacuum. There is a script called install_vacuum.sh that with a single command, can build the server to my spec from a base install of Ubuntu 24.04. it has functions to install base packages from repositories, add new repositories, set up users, create config files for NFS, smb, fstab, crontab, etc... once an NFS server exists on my network, any other server could be my docker host. My docker host is set up from a script install_containers.sh. as with before, it does all the things to get me a basic docker host, firewalled, and configured for persistence via my NFS server. It also has functions to create and start docker containers for all of my workflows (Plex, webserver, CA, etc), and if those containers don't exist, it will build a docker image for said workflow based on a standardized format (you guessed it) bash build script for the containers. There is automation via cron on whatever host runs docker to build and update the containers once a week, bare-metal servers update themselves nightly, rebooting when necessary via unattended-upgrades.

Basically, you break everything down into the simplest function possible, have everything defined via variables in shared configurations that everything sources before running, and you have higher and higher level functions call other functions until you have a single function that cascades into a functioning system. Does that make sense?

[-] Cyber@feddit.uk 1 points 6 hours ago
[-] Dran_Arcana@lemmy.world 2 points 5 hours ago

I use ansible on one of my side projects; I use puppet at work. It's the same reason I use raw docker and not rancher+rke2... it's not about learning the abstractions; it's about learning the fundamentals. If I wanted a simple abstraction I'd have deployed truenas and Linuxsserver containers instead of Taco Bell programming everything myself.

[-] nu11@sh.itjust.works 3 points 16 hours ago
[-] Dran_Arcana@lemmy.world 2 points 15 hours ago

Have you started collecting your notes into scripts?

this post was submitted on 11 Jan 2025
63 points (100.0% liked)

Selfhosted

41009 readers
526 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 2 years ago
MODERATORS