this post was submitted on 13 Mar 2026
1327 points (99.0% liked)

Selfhosted

56958 readers
1217 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 
(page 2) 50 comments
sorted by: hot top controversial new old
[–] FauxLiving@lemmy.world 23 points 1 day ago

The comments in this thread have collectively created thousands of person-hours worth of work for us all...

[–] nucleative@lemmy.world 17 points 1 day ago* (last edited 1 day ago) (2 children)

Never run:

docker compose pull
docker compose down
docker compose up -d

Right before the end of your day. Ask me how I know 😂

[–] shym3q@programming.dev 9 points 1 day ago (1 children)

compose up will automatically recreate with newer images if the new one were pulled. so there is no need for compose down btw

[–] nucleative@lemmy.world 2 points 19 hours ago

You're right. I got in the habit of doing that because I'm endlessly tweaking my .env files and I don't think those reload unless you shut down first

load more comments (1 replies)
[–] tal@lemmy.today 36 points 1 day ago (2 children)

All of those systems in your homelab...they aren't all pulling down their updates multiple times over your network link, right? You're making use of a network-wide cache? For Debian-family systems, something like Apt-Cacher NG?

Oh. You're not. Well, that's probably okay. I mean, not everyone can have their environment optimized to minimize network traffic.

load more comments (2 replies)
[–] fleem@piefed.zeromedia.vip 9 points 1 day ago (3 children)

heck i really wish we could all throw a party together. part swap, stories swap. show off cool shit for everyone to copy.

help each other fill in the missing pieces

y'all seem like cool peeps meme-ing about shit nobody else gets!

time to test the backups!

[–] irmadlad@lemmy.world 6 points 1 day ago

time to test the backups!

Always a white knuckle event for me

[–] Ensign_Crab@lemmy.world 6 points 1 day ago

You just described a convention.

[–] moonpiedumplings@programming.dev 3 points 23 hours ago

https://infosecmap.com/

https://wiki.hackerspaces.org/List_of_Hacker_Spaces

Also check out meetup.com for linux user groups and other events.

[–] rumba@lemmy.zip 7 points 1 day ago

Nothing to install? Not with that attitude!

Start a 10" rack.

[–] Fedegenerate@fedinsfw.app 15 points 1 day ago

Going into spring/summer that's ideal, I wanna go places do things. Mid winter, I'm feature creeping till something breaks.

[–] irmadlad@lemmy.world 5 points 1 day ago

OP, totally understand, but this is a level of success with your homelab. Nothing needs fiddling with. Now, there is a whole Awesome Self Hosted list you could deploy on a non-production server and run that through the paces.

[–] tal@lemmy.today 18 points 1 day ago* (last edited 1 day ago) (1 children)

You have an intrusion detection system set up, right? A server watching your network's traffic, looking for signs that systems on your network have been compromised, and to warn you? Snort or something like that?

Oh. You don't. Well, that's probably okay. I mean, probably nothing on your network has been compromised. And probably nothing in the future will be.

load more comments (1 replies)
[–] tal@lemmy.today 13 points 1 day ago (1 children)

You have all your devices attached to a console server with a serial port console set up on the serial port, and if they support accessing the BIOS via a serial console, that enabled so that you can access that remotely, right? Either a dedicated hardware console server, or some server on your network with a multiport serial card or a USB to multiport serial adapter or something like that, right? So that if networking fails on one of those other devices, you can fire up minicom or similar on the serial console server and get into the device and fix whatever's broken?

Oh, you don't. Well, that's probably okay. I mean, you probably won't lose networking on those devices.

load more comments (1 replies)
[–] tal@lemmy.today 14 points 1 day ago

All of your systems are set up, but are they capable of being redeployed using a configuration management software package? Ansible or something like that?

Oh. They're not. Well, that's probably okay. I mean, you could probably go manually reproduce configurations, more or less.

[–] AkatsukiLevi@lemmy.world 9 points 1 day ago (1 children)

Do you have a spinning fish display in front of your homelab server, right? We all know the spinning fish improves performance and security, it is a indispensable part of homelabbing

load more comments (1 replies)
load more comments
view more: ‹ prev next ›