<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blogs :: Homelab Documentation</title><link>https://ede1998.codeberg.page/homelab-docs/blog/index.html</link><description/><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 04 Sep 2026 20:58:01 +0200</lastBuildDate><atom:link href="https://ede1998.codeberg.page/homelab-docs/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Documenting Secrets</title><link>https://ede1998.codeberg.page/homelab-docs/blog/01_secrets/index.html</link><pubDate>Fri, 04 Sep 2026 20:58:01 +0200</pubDate><guid>https://ede1998.codeberg.page/homelab-docs/blog/01_secrets/index.html</guid><description>Just writing secrets in plain text into my documentation is bad, especially since I intend to just publish it on the internet.&#10;On the other hand, homelab documentation often benefits from being able to include secrets: Server addresses, passwords and access tokens are closely interlinked with workflows such as updating packages that this kind of documentation describes.&#10;To solve this conflict, I’m not including secrets in my documentation directly. I save those in my Bitwarden password safe instead. Bitwarden supports direct links to items, so that’s already much better than simply referencing the item by name. However, these direct links only open the web interface, which I don’t typically use. This can be improved a bit more.</description></item><item><title>Hello World!</title><link>https://ede1998.codeberg.page/homelab-docs/blog/00_hello_world/index.html</link><pubDate>Fri, 04 Sep 2026 20:57:52 +0200</pubDate><guid>https://ede1998.codeberg.page/homelab-docs/blog/00_hello_world/index.html</guid><description>This is a first test post. I finally managed to create a homelab documentation setup.&#10;Yay!</description></item></channel></rss>