Of course now he wants to cooperate

Removed by mod

Sounds like it’s time to give a little insider info on the company network to hacking groups.

CEOs. Name them. Shame them.

Lot of knowledge to just throw out there, Sundar.

Let’s hope your documentation can handle it, or a whole lot of important stuff is going to take forever to fix if/when it breaks

My Proxmox server is called ARCADE and each VM is named after a game. Currently we have:

• SpyHunter (PiHole and WireGuard VPN)
• Pacman (Ubuntu Server w/ Dashy, Syncthing, Portainer, and NextCloud inside Docker)
• MsPacMan (Ubuntu server for failover purposes. Still under construction)
• CrazyTaxi (Windows Desktop)
• MissleCommand (Linux Desktop)
• MonkeyIsland (qBitTorrent)

Nvidia, good call. Take the easy win

Checks out

Sure.

• Hardware
• Software

I left everything in, so no doubt there’s stuff in there specific to my vault you won’t need like metadata - adjust these to your needs or use them as a starting point for something new. There’s no network device template, I usually use the hardware one and just delete the irrelevant bits.

deleted by creator

I’ve been using Obsidian for a lot of other purposes for a couple years now, so I was comfortable adding my documentation into my existing vault there. I made a couple templates that I fill out for any hardware/software/networking equipment.

Since the app’s selling point is storing all your notes in plain text I wouldn’t put anything security-related in there without some encrypted container. I use KeePass for that part, and keep the file it generates in the same folder as Obsidian so I can link to it within notes. Click the link in the note, KeePass opens the vault and asks for its password.

Where did you get this picture of me?

It’s the kind of thing that’s easy to start and hard to continue. Time will tell, but I hope we can develop the kind of community values here that will grow with scale, rather than shrink