MastodonTech.de

DajeLinux :linux: :fedilug:Sperimentare Alpine Linux su un vecchio Chromebook convertito a Linux è stato piuttosto "illuminante". Probabilmente seguiranno ulteriori articoli in merito; ma intanto iniziamo a saggiare le caratteristiche principali e lo script per l'installazione di quello che io ho chiamato in modo provocatorio "Il sistema operativo universale".<a href="https://dajelinux.it/archivio/alpine-linux-1" rel="nofollow noopener" translate="no" target="_blank">https://dajelinux.it/archivio/alpine-linux-1</a><a href="https://mastodon.uno/@linux" class="u-url mention" rel="nofollow noopener" target="_blank">@linux</a> <a href="https://diggita.com/c/linux" class="u-url mention" rel="nofollow noopener" target="_blank">@linux@diggita.com</a> <a href="https://diggita.com/c/opensource" class="u-url mention" rel="nofollow noopener" target="_blank">@opensource</a> <a href="https://diggita.com/c/tecnologia" class="u-url mention" rel="nofollow noopener" target="_blank">@tecnologia</a> <a href="https://mastodon.uno/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a> <a href="https://mastodon.uno/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.uno/tags/unolinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#unolinux</a> <a href="https://mastodon.uno/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mastodon.uno/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.uno/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://mastodon.uno/tags/floss" class="mention hashtag" rel="nofollow noopener" target="_blank">#floss</a> <a href="https://mastodon.uno/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://mastodon.uno/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a>

MikaI've finally completed most of the guides I was planning on adding to my <a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener" target="_blank">#Homelab</a> Wiki - now it's got guides on setting up <a href="https://sakurajima.social/tags/Portainer" rel="nofollow noopener" target="_blank">#Portainer</a>, <a href="https://sakurajima.social/tags/Immich" rel="nofollow noopener" target="_blank">#Immich</a>, <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a>, <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a>, <a href="https://sakurajima.social/tags/OpenMediaVault" rel="nofollow noopener" target="_blank">#OpenMediaVault</a> (<a href="https://sakurajima.social/tags/OMV" rel="nofollow noopener" target="_blank">#OMV</a>), and even <a href="https://sakurajima.social/tags/HomeAssistant" rel="nofollow noopener" target="_blank">#HomeAssistant</a> - all of these (besides Jellyfin and ErsatzTV, those are on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a>) are hosted on my <a href="https://sakurajima.social/tags/RaspberryPi" rel="nofollow noopener" target="_blank">#RaspberryPi</a> in my homelab. Most importantly though, I've organised the wiki a lil better - into different courses. The first course details the type of hardware you're going to want to assemble - a beefy server (with only consumer parts) or a mini server (i.e. an <a href="https://sakurajima.social/tags/SBC" rel="nofollow noopener" target="_blank">#SBC</a>), or whether you'd like to deploy a <a href="https://sakurajima.social/tags/NAS" rel="nofollow noopener" target="_blank">#NAS</a>, followed by a course to setting up and managing a hypervisor (including <a href="https://sakurajima.social/tags/ESXi" rel="nofollow noopener" target="_blank">#ESXi</a>, but really, use Proxmox - which is <a href="https://sakurajima.social/tags/FOSS" rel="nofollow noopener" target="_blank">#FOSS</a> and plain better). There's also a whole course on all sorts of 'host deployment environments' (i.e. where your application is hosted on, like <a href="https://sakurajima.social/tags/VM" rel="nofollow noopener" target="_blank">#VM</a>, <a href="https://sakurajima.social/tags/Docker" rel="nofollow noopener" target="_blank">#Docker</a>, <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a>, and <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener" target="_blank">#LXC</a>) you could have in your homelab. (One of the) Most importantly, a course on networking - which covers valuable topics like setting up a domain, free or paid, and setting up a reverse proxy for serving your hosted applications publicly, securely. There's still some stuffs I gotta add, like a complete guide on setting up <a href="https://sakurajima.social/tags/TrueNAS" rel="nofollow noopener" target="_blank">#TrueNAS</a> (which I've set up for many years at this point, without much documentation on how I did it - so I gotta find an opp to replicate it, when I have extra hardware maybe), but I'm pretty happy with it at this point. If you're planning to get into homelabbing, or even if you're already in it - maybe check it out :blobfoxcat: 🔗 <a href="https://github.com/irfanhakim-as/homelab-wiki" rel="nofollow noopener" target="_blank">https://github.com/irfanhakim-as/homelab-wiki</a> RE: <a href="https://sakurajima.social/notes/a9so79m6ze" rel="nofollow noopener" target="_blank">https://sakurajima.social/notes/a9so79m6ze</a>

prozak<a href="https://techhub.social/@ironicbadger" class="u-url mention" rel="nofollow noopener" target="_blank">@ironicbadger</a> I feel your freedom, albeit not moving I’ve been systematic doing the same. Welcome to the just enough <a href="https://corteximplant.com/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> to have fun club

BennyI initially registered for <a href="https://mastodontech.de/tags/Tailscale" class="mention hashtag" rel="tag">#Tailscale</a> using my GitHub account, but I'm considering migrating to <a href="https://mastodontech.de/tags/PocketID" class="mention hashtag" rel="tag">#PocketID</a> and my own domain. However, I have some concerns about losing access to Tailscale if PocketID becomes unavailable. Even worse, I'm worried about the possibility of unauthorized access. <a href="https://mastodontech.de/tags/homelab" class="mention hashtag" rel="tag">#homelab</a>

Jan Wildeboer 😷:krulorange:And because it's called podman for a reason, the CA now runs in a pod, so I can add more containers to it, if needed. I will update the gists to reflect that change. (UPDATE: Done)4/4<a href="https://social.wildeboer.net/tags/nerdcert" class="mention hashtag" rel="nofollow noopener" target="_blank">#nerdcert</a> <a href="https://social.wildeboer.net/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://social.wildeboer.net/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHost</a> <a href="https://social.wildeboer.net/tags/x509" class="mention hashtag" rel="nofollow noopener" target="_blank">#x509</a> <a href="https://social.wildeboer.net/tags/CA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CA</a>

Matthias KleinGerman Version (english below)Ich habe gerade "GTS-HolMirDas" als Open Source Projekt veröffentlicht.Ein RSS-basiertes Content-Discovery-Tool für kleinere GoToSocial-Instanzen. Es hilft dabei, die föderierte Timeline zu füllen, ohne auf traditionelle Relays angewiesen zu sein.Was es macht:<ul><li>Verarbeitet RSS-Feeds verschiedener Fediverse-Instanzen</li><li>Docker-Deployment mit simplem .env-Setup</li><li>Sehr ressourcenschonend (kompletter Stack mit GoToSocial + FediFetcher: ~450MB RAM)</li><li>Zeigt detaillierte Statistiken</li></ul>Inspiriert von Alice's HolMirDas für Misskey (<a href="https://mkultra.x27.one/@aliceif" class="u-url mention" rel="nofollow noopener" target="_blank">@aliceif</a>), angepasst für GoToSocial mit Docker-Integration.Repository: <a href="https://git.klein.ruhr/matthias/gts-holmirdas" rel="nofollow noopener" target="_blank">https://git.klein.ruhr/matthias/gts-holmirdas</a>Läuft bei mir produktiv und verarbeitet stündlich Content von 80 RSS-Feeds. Falls jemand sowas braucht - einfach ausprobieren.Feedback gerne willkommen! 🚀 Just released "GTS-HolMirDas" as an open source project.RSS-based content discovery tool for smaller GoToSocial instances. Helps populate your federated timeline without relying on traditional relays.What it does:<ul><li>Processes RSS feeds from various Fediverse instances</li><li>Docker deployment with simple .env setup</li><li>Very resource-efficient (complete stack with GoToSocial + FediFetcher: ~450MB RAM)</li><li>Shows detailed statistics</li></ul>Inspired by Alice's HolMirDas for Misskey (<a href="https://mkultra.x27.one/@aliceif" class="u-url mention" rel="nofollow noopener" target="_blank">@aliceif</a>), adapted for GoToSocial with Docker integration.Repository: <a href="https://git.klein.ruhr/matthias/gts-holmirdas" rel="nofollow noopener" target="_blank">https://git.klein.ruhr/matthias/gts-holmirdas</a>Running in production here, processing content from 80 RSS feeds hourly. If anyone needs something like this - just give it a try.Feedback welcome! 🚀<a href="https://me.klein.ruhr/tags/gotosocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoToSocial</a> <a href="https://me.klein.ruhr/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://me.klein.ruhr/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a> <a href="https://me.klein.ruhr/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://me.klein.ruhr/tags/contentdiscovery" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContentDiscovery</a> <a href="https://me.klein.ruhr/tags/rss" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSS</a> <a href="https://me.klein.ruhr/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://me.klein.ruhr/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#Homelab</a> <a href="https://me.klein.ruhr/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://me.klein.ruhr/tags/smallinstance" class="mention hashtag" rel="nofollow noopener" target="_blank">#SmallInstance</a> <a href="https://me.klein.ruhr/tags/federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Federation</a>

Jan Wildeboer 😷:krulorange:So now my Cute Homelab has its own CA (Certificate Authority), neatly packed in a container that works with certbot and I can use valid certificates all over my homelab and local network for more experiments :) And it only uses 17MB of RAM.3/4<a href="https://social.wildeboer.net/tags/nerdcert" class="mention hashtag" rel="nofollow noopener" target="_blank">#nerdcert</a> <a href="https://social.wildeboer.net/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://social.wildeboer.net/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHost</a> <a href="https://social.wildeboer.net/tags/x509" class="mention hashtag" rel="nofollow noopener" target="_blank">#x509</a> <a href="https://social.wildeboer.net/tags/CA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CA</a>

Jan Wildeboer 😷:krulorange:The certbot part works and is now also documented as gist at <a href="https://codeberg.org/jwildeboer/gists/src/branch/main/2025/20250729CertbotOwnCA.md" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/jwildeboer/gists/src/branch/main/2025/20250729CertbotOwnCA.md</a>2/4<a href="https://social.wildeboer.net/tags/nerdcert" class="mention hashtag" rel="nofollow noopener" target="_blank">#nerdcert</a> <a href="https://social.wildeboer.net/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://social.wildeboer.net/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHost</a> <a href="https://social.wildeboer.net/tags/x509" class="mention hashtag" rel="nofollow noopener" target="_blank">#x509</a> <a href="https://social.wildeboer.net/tags/CA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CA</a>

Miroslav StankicThis is why you need a local photon host for <a href="https://mastodon.social/@dawarich" class="u-url mention" rel="nofollow noopener" target="_blank">@dawarich</a>. Using the default, public api, you get around a 97% failure rate, due to rate limiting. This would've taken days, if not weeks, with free rate limits. Under full load, photon-docker is using around a gig of RAM and 1-2% CPU. The only possible issue could be storage, because the data requires some 200 gigs of storage.<a href="https://mastodon.social/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://mastodon.social/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> <a href="https://mastodon.social/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://mastodon.social/tags/Dawarich" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dawarich</a>

ThibCredentials shouldn't be around in plain text files. But I also don't want to set up a fully fledged credentials management solution for my homelab.Wouldn't it be nice to dynamically load the credentials I need when I step into my work directory, and remove then when I leave it?Let's use <a href="https://fosstodon.org/@bitwarden" class="u-url mention" rel="nofollow noopener" target="_blank">@bitwarden</a> and direnv to keep credentials safe in all simplicity!<a href="https://ergaster.org/posts/2025/07/28-direnv-bitwarden-integration/" rel="nofollow noopener" translate="no" target="_blank">https://ergaster.org/posts/2025/07/28-direnv-bitwarden-integration/</a><a href="https://mamot.fr/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://mamot.fr/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://mamot.fr/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a>

Jan Wildeboer 😷:krulorange:Added a few new gists on setting up a homelab Certificate Authority (CA) on a RHEL 10 machine with step-ca as podman container in preparation for a longer blogpost on the topic.- Basic Step CA setup as podman container - Manually add a root CA certificate to RHEL 10 - Manually generate certificates with Step CA<a href="https://codeberg.org/jwildeboer/gists/src/branch/main" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/jwildeboer/gists/src/branch/main</a>Tomorrow I will add a gist on using certbot to renew certificates in my homelab using that CA.1/4<a href="https://social.wildeboer.net/tags/nerdcert" class="mention hashtag" rel="nofollow noopener" target="_blank">#nerdcert</a> <a href="https://social.wildeboer.net/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://social.wildeboer.net/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHost</a> <a href="https://social.wildeboer.net/tags/x509" class="mention hashtag" rel="nofollow noopener" target="_blank">#x509</a> <a href="https://social.wildeboer.net/tags/CA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CA</a>

Martin 🇪🇺<a href="https://mastodon.social/@renef" class="u-url mention" rel="nofollow noopener" target="_blank">@renef</a> haha. Ich mache das andersherum. Teleport um einfach mal eben flott aufs <a href="https://norden.social/tags/Homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#Homelab</a> zuzugreifen. Und tailscale läuft als Backup auf allen Maschinen... 😬

DavidI am running a vps (wireguard ipv4 vpn tunnel), two rpis for dns and a ubuntu vm on proxmox as my homeserver. I am thinking about moving all of these to nixos for obvious reasons (declarative config stored in repo, etc.) Anyone with a similar already working setup? Any suggestions/articles you can recommend? Currently basically all is deployed via docker. Would you recommend switching to the nix packages? <a href="https://chaos.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://chaos.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> <a href="https://chaos.social/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#nixos</a>

Niklaus 'vimja' HoferFinally krimped the last few missing cables for my living room rack. Now it looks all tidy again. Should have done that a lot sooner.<a href="https://tooting.ch/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a>

Nico Jensen :fcsp2:Hab ich hier jemanden der erfahrung mit Vodafone Kabel und IPv6 hat? <a href="https://elbmatsch.de/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://elbmatsch.de/tags/vodafone" class="mention hashtag" rel="nofollow noopener" target="_blank">#vodafone</a>

jhxHomepage is a really nice dashboard with tons of functionality. Just fiddled a little with and i'm impressed! 😎 (Screenshot attached with my current setup)Link: <a href="https://gethomepage.dev/" rel="nofollow noopener" translate="no" target="_blank">https://gethomepage.dev/</a><a href="https://fosstodon.org/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> <a href="https://fosstodon.org/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://fosstodon.org/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://fosstodon.org/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a>

Matthias Klein<a href="https://gofer.social/@daj" class="u-url mention" rel="nofollow noopener" target="_blank">@daj</a> <a href="https://gts.tumfatig.net/@joel" class="u-url mention" rel="nofollow noopener" target="_blank">@joel</a> <a href="https://tagpush.app/@gotosocial" class="u-url mention" rel="nofollow noopener" target="_blank">@gotosocial</a> Thanks for creating TagPush, David! I appreciate the work you're putting into solving the small instance discovery problem.You're absolutely right about FediBuzz being erratic - I've noticed that too. Some days are content-heavy, others pretty quiet.I actually tried both services and found different strengths:TagPush: More reliable/consistent, but limited tag selection (totally understandable for a one-person project!)FediBuzz: Broader tag coverage (I need things like <a href="https://me.klein.ruhr/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a>, <a href="https://me.klein.ruhr/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a>, <a href="https://me.klein.ruhr/tags/fediadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediadmin</a> and also <a href="https://me.klein.ruhr/tags/nrw" class="mention hashtag" rel="nofollow noopener" target="_blank">#nrw</a> and other hashtags for local content), but yeah, the reliability can be hit-or-miss.For my use case I ended up sticking with FediBuzz mainly because I need some specific tech/local tags that aren't available on TagPush yet. But I really like TagPush's consistent delivery approach - that "fire-hose" problem you mention with relays is real!Question: Are you planning to expand the tag list, or keeping it intentionally curated to maintain quality? I'd love to see tags like <a href="https://me.klein.ruhr/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a>, <a href="https://me.klein.ruhr/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a>, <a href="https://me.klein.ruhr/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> if that fits your vision!Really appreciate both services existing - competition/alternatives are always good for the ecosystem! 🚀

tjhowseYesterday I noticed that the pool pump wasn't running. I checked the power consumption logs and found it hasn't been running for a few days. This is very bad! High risk of soup pool.After fixing the issue with the pump, I set up an automation in <a href="https://howse.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#homeassistant</a> : At 09:30 every day, check the power consumption of the pump. Send an alert to my phone if it's less than 1.5kW.All thanks to <a href="https://howse.social/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a>!<a href="https://howse.social/tags/hass" class="mention hashtag" rel="nofollow noopener" target="_blank">#hass</a> <a href="https://howse.social/tags/homeautomation" class="mention hashtag" rel="nofollow noopener" target="_blank">#homeautomation</a> <a href="https://howse.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://howse.social/tags/esphome" class="mention hashtag" rel="nofollow noopener" target="_blank">#esphome</a>

Paco Hope #resistVery strange behavior from <a href="https://infosec.exchange/tags/TrueNAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrueNAS</a> Scale tonight. First time this particular thing has ever happened. It has completely stopped responding on it's main IP address. I have 4 different VMs all running on it (each has its own IP address). All the VMs are fine. They're running normally, they're reachable, they're running fine. But I can't get to the main IP for the main system via SSH, HTTPS, nothing.So the physical box and an awful lot of the networking is running just fine. DHCP server says it renewed its IP address less than 24 hours ago. So I will have to go drag a monitor and keyboard into the garage to reboot it. Weird.<a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a>

UrzlI'm just wildly pleased with the switch to <a href="https://mastodon.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NixOS</a>.My Pi was super dead after the latest storm related power issues, even the external drive doesn't power up properly anymore.So I hacked together a deploy script and repurposed the mini PC I wasn't actually using. A couple days later and now I've got <a href="https://mastodon.social/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeAssistant</a> back up in a container, centralized my admin and backed it up to version control. "Maybe someday" automation items were accessible immediately. I love it.<a href="https://mastodon.social/tags/homeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homeLab</a> <a href="https://mastodon.social/tags/geekery" class="mention hashtag" rel="nofollow noopener" target="_blank">#geekery</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#homelab