Gnótt Documentation 🌿
Community driven documentation for all the nerdy things we actually use: servers, Raspberry Pis, media setups, panels, operating systems and all the little tricks we don't want to forget.
A cozy place for all those “how did I set this up again?” moments.
What lives here? 🌍
Gnótt Docs is a hub for practical infrastructure, homelab setups and media configs. No marketing fluff, just honest notes, step-by-step guides and lessons learned the hard way.
🖥️ Servers & homelab
Hypervisors, containers, reverse proxies, backups, monitoring and everything else humming away in your rack or on a shelf. From first install to “I finally automated this”.
🍓 Raspberry Pis & tiny boxes
Headless setups, kiosks, small services and sensors, perfect for home automation, dashboards and “why not?” projects that start small and somehow become critical.
📺 Media: Emby & friends
Media servers, transcoding, library structure and network tricks that keep your movies, shows and music fast, tidy and accessible without turning into chaos.
📊 Panels & control
Pelican Panel, game server panels and other control planes. Clean structure, sane defaults and security tips so you can host things without constantly firefighting.
🐧 Operating systems
Notes on Linux, Windows, BSD and more. Installs, hardening, useful tools and small tweaks that make your daily workflow smoother instead of more annoying.
🧩 Little tricks & “good to know”
Handy one-liners, small scripts, copy-paste snippets and weird quirks that don't deserve a full article but absolutely deserve not to be lost in some random note app.
Community driven, not polished marketing 🤎
Gnótt is meant to be a living archive. Things get updated, rewritten and improved as we learn more and as we break more things in new and interesting ways.
- 📌 Document your own setups and experiments
- 🪲 Capture bugs, workarounds and “don't do this” stories
- 🔁 Come back later and actually remember what you did
The goal is simple: future-you should be able to say “oh nice, past-me actually wrote this down”.
How to contribute
Exact workflow depends on how the repo is set up, but usually it looks something like this:
- Pick an area you know (or just explored)
- Create or update a page inside
docs/ - Commit & push your changes or open a pull request
Tiny notes are welcome too. You don't have to write a huge guide for it to be helpful to someone else.