this post was submitted on 18 May 2025
134 points (100.0% liked)

Selfhosted

46685 readers
303 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
 

Hello, how do you document your home lab? Whether it's a small server or a big one with firewall and more nodes. I have a small pc with Proxmox and there I have a VM with OpnSense. After I've entered my VPN as a interface in OpenSense, I noticed that I slowly lose the overview with the different rules that I have built in my firewall. And I know that my setup is relatively easy in comparison to others here in this community. I want to have a quick Overview at the various VMs, like the Lxc container, Docker containers that I have in this and the IP addresses that I have assigned to them. I search for a simple an intuitiv way for beginners.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 18 points 6 days ago* (last edited 6 days ago) (4 children)

I operate on the philosophy that it is better for me to relearn things than lean on old documentation that may no longer be accurate/relevant.

The best way to implement a safe connection to my home lab today might not be the safest way tomorrow.

Old dog, new tricks, etc.

Also! Your documentation is an attackers wet dream.

NB: this philosophy doesn't scale.

[–] [email protected] 1 points 3 days ago (1 children)

while security might be compromised if an attacker found your documentation, it could equally be compromised by having zero documentation

the easier it is for you to get things back up and running in the event of a data loss / corrupted hard drive / new machine / etc, the less likely you are to forget any crucial steps (eg setting up iptables or ufw)

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

Having 0 documentation doesn't mean you have no DLP strategy. That's amateur hour.

And again, NB: this does not scale.

[–] [email protected] 2 points 6 days ago

I do this continually for work as well, I approach every new project assuming best practice or approach options have changed. It doesn't matter how experienced I am in what I'm doing, I still loop back and check.

It's such an automatic thing I don't even think about it, but honestly not sure if it's because of interest or because of fear of being called out for doing something wrong lol

[–] [email protected] 8 points 6 days ago

I'm gonna try this neat trick at work

[–] [email protected] 24 points 6 days ago (1 children)
[–] [email protected] 3 points 5 days ago

What I don't know, no phisher can get out of me!