this post was submitted on 01 Feb 2026
62 points (98.4% liked)

Selfhosted

55494 readers
711 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
 

It's been a while, let's go! Any major fuckups lately or smooth sailing?

I had to change the local DNS setup yesterday. I finally installed my wife Linux Mint and wanted to set her up for Vaultwarden real quick which became an hour long debug session since apparently CNAME entries for hostnames don't work as I thought. Never came up the recent year as all my machines took it, but resolved refused to and so I eventually deleted the entries in the Pihole and created them as A records pointing to the VM with the reverse proxy, hoping I won't need to change the IP anytime soon. It's always DNS!

In other news I think I moved all my local dockered services to forgejo+komodo now and applying updates by merging renovate MRs still feels super smooth. I just updated my calibre web automated with a single click. Only exception is home assistant where I have yet to find a good split in what to throw in a docker volume and what to check in git and bindmount.

you are viewing a single comment's thread
view the rest of the comments
[–] tofu@lemmy.nocturnal.garden 3 points 1 day ago (1 children)

If you want to go all in, get some plug that measures the energy! Also let's you directly see the effects of turning stuff on/off. My last server went up 3W when I started using the second network interface! Let drives go to sleep, play with C-States, etc

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

I had a post a while back about what I was doing to cut costs.

  • TLP: Adjusts CPU frequency scaling, PCI‑e ASPM, SATA link power‑management
  • Powertop: Used to profile power consumption and has a tune feature sudo powertop --auto-tune
  • cpufrequtils: Used to manage the CPU governor directly
  • logind.conf: Can be used to put the whole server to sleep when idle

After doing all of that, which does help out during operational hours, I decided to save 10-12 hours of consumption by just shutting it down. The old 'turn the light out if you're not in the room' concept. Right now I am manually booting the server, and it doesn't take that long to resume operations. However, why not employ some automation and magic packets to fire it back up in the morning.

ETA: I do have a watt meter on the server.

[–] tofu@lemmy.nocturnal.garden 2 points 1 day ago (1 children)

Sounds good! Are you on SSD or HDD?

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

The OS lives on an SSD and I have two aux drives. One is HDD, but it is a samba share for Navidrome, so it's not like it's spinning constandly. Everything gets a 3,2,1 backup.

ETA: Now that you mention it, I guess I could employ a park(?) for the HDD before shutting down.