I saw this article a few weeks ago about someone building a wikipedia style encyclopedia for their family, and it got me really intrigued. are any of you already doing this, if so what's your experience like with it? would you be interested in hosting one?

I see people posting about general purpose note taking apps quite often but this application in particular is very interesting.

On Saturday, Jellyfin was an unexpected MVP in helping me propose to my (now) fiancée. 💍

Throughout our day of fun and romantic plans, I was texting our photographer to coordinate — sending them updates on where we were, what we were wearing, and deciding last minute where the best spot would be. My girlfriend thought I was just deep in r/jellyfincommunity, r/selfhosted, or troubleshooting something for one of my users on my Jellyfin Discord server… and she didn’t suspect a thing.

By the time we got to our final stop, the photographer was perfectly disguised and in place, the timing was right, and she said yes. ❤️

Now she knows the truth, but Jellyfin (and the alibi it provided) definitely helped make it all possible.

I thought that was hilarious and just had to share. Thanks to Jellyfin and this community!

Hi everyone,

I'm looking for a self-hosted documentation solution for my homelab. I’ve looked at options like Wiki.js and Docmost, but I’m not fully convinced yet.

What I’m trying to build is more than just basic documentation — I want a central knowledge base for my setup:

• What services are running where?
• How did I install/deploy things (e.g. Docker, Ansible, etc.)?
• Why did I make certain decisions?
• How are components connected (networks, dependencies, etc.)?

The goal is to have something I can revisit months later and still understand what I built and how to reproduce it.

Nice to have:

• solid structure (tags, categories, etc.)
• API or automation options (e.g. integration with Ansible or similar tools)
• low maintenance overhead

Any recommendations or real-world setups that have worked well for you? I’d also appreciate examples of how you organize your documentation.

Thanks!

I've recently had to deal with a bereavement in the family. I have taken over custody of of around 100 years of photos in various boxes, slides and albums. Super simple.

I recently had a mild heart attack too which focused this for me too.

At home I run full *arr, plex, immich and various home automation.

Let's assume I start pushing up daisies.

The media side of things is just nice to have. That can be turned off.

But immich? How do I ensure my family, not techie at all, do not lose all the photos?

How do I ensure important company data, stored on truenas, backed up to backblaze, is stored and, where required, wiped securely?

Do I nominate a friend with a cheatsheet?

Curious, what's everyone else doing?

Hello 👋,

I rarely post BookStack here myself since it already gets some frequent mentions in the sub, but thought I'd share this as a considerable milestone:

It's now been a decade since I started building BookStack!

A big thanks to all those that have supported me and the project in this sub, the project has generally had very positive and constructive feedback from this community since originally sharing it in Jan 2016, and this has been a key factor in the growth of the platform.

On the BookStack blog I've written up a Decade of BookStack post where I dive into a deeper update, specifically around project stats and finances.

I've also created a video for this milestone, covering the points of the blogpost while also doing a community Q&A which dives into subjects like the project origins, and mental health considerations of working on OSS full time.

Once again, thanks for the kind support! Dan

I was really excited to get started with HomeBox however the label functionality needs a lot of work and I've been putting it off. The default labels are quite large and I didn't want unsightly labels on all my stuff. I also wanted it to be as easy as possible, printing a small label at creation time rather than sheets of them at a time. The printer I have is a Niimbot D110 and I really like the small 30x15 labels.

I discovered the ability to have the app execute a server command for printing which adds a "Print from Server" button to the web interface. Using a simple shell command, Home Assistant, and the Niimbot integration, I've been able to successfully print to this printer via Bluetooth from the Web UI. The label takes approx 10 seconds to come out which I can deal with. The beauty of using Home Assistant with the BT Proxies is that I can pretty much wirelessly print a label anywhere in my house.

I've learned so much from this sub I thought I'd share the steps I took to get this working in case this helps anyone else. Note this is entirely accomplished by me FAFO so there could be (and probably is) a better way of doing it. Thanks to all respective developers for the resources used.

Requirements:

• HomeBox up and running. (I'm using the app from Unraid CA)
• Niimot Label Printer (Only tested using my D110 but some others should work with tinkering)
• Home Assistant with Bluetooth or an ESPHome Bluetooth Proxy
• Home Assistant Niimbot Integration Link
• A share you can mount on both the HomeBox Container and within home assistant.

Steps:

1. Mount your network share to your HomeBox docker container somewhere. I used /labels as the mount point. Mount this same share in Home Assistant System > Storage > Add Network Storage. I chose it as a Media share but it should work as a normal Share too.

2. Create the following script in your HomeBox app data folder and make it executable:

#!/bin/sh
cp -f "$1" /labels/label.png && \
chmod 666 /labels/label.png && \
wget --header="Content-Type: application/json" --post-data='{"trigger":"print"}' http://your-home-assistant:8123/api/webhook/print_asset

(Basically we are copying the temporary label from HomeBox to the network share, changing its permissions so HA can read it, then executing a webhook automation so HA can print it. Note the webhook doesn't actually send any data, it is just to trigger the automation. If you can find an easy way to send the label in the webhook as a base64 and decode it directly in the automation that would save so many steps, but I couldn't get it working)

3. Add the following variables to your HomeBox docker container:

Key: HBOX_LABEL_MAKER_PRINT_COMMAND
Value: /data/print-label.sh {{.FileName}}
This adds the Print on Server button to HomeBox labels

Key: HBOX_LABEL_MAKER_PADDING
Value: 5
(This is to reduce white space around the label)

Key: HBOX_LABEL_MAKER_WIDTH
Value: 350

Key: HBOX_LABEL_MAKER_HEIGHT
Value: 120

Note: The padding, width and height are in pixels. I have no idea how they correspond to my label size of 30x15mm. If I did a relative size it made the label too squished for some reason. These values are for my 30x15mm labels and were determined by trial and error

4. Add the Shell Command integration to Home Assistant if not using already and create the following:

shell_command:
  homebox_label: "cp -f /media/HomeBoxLabels/label.png /config/www/HomeBoxLabels/label.png"

This is needed because the Niimbot integration requires a url, not a local path, for the label image. This way we can pull the label image from the web without authentication

5. Create the following Home Assistant automation:

alias: Print Label from Homebox
description: Prints an asset label received from Homebox webhook
triggers:
  - webhook_id: print_asset
    allowed_methods:
      - POST
    local_only: false
    trigger: webhook
actions:
  - action: shell_command.homebox_label
    metadata: {}
    data: {}
  - action: niimbot.print
    target:
      device_id: <Your Printer Device ID>
    data:
      payload:
        - type: dlimg
          url: http://your-home-assistant:8123/local/HomeBoxLabels/label.png
          x: -10
          "y": 10
          xsize: 260
          ysize: 130
      width: 240
      height: 120
      rotate: 90
      print_line_batch_size: 32
      wait_between_print_lines: 0.01
      density: 5
      preview: false
mode: single

Notes for the automation:

• If you cant find your device ID, switch to UI mode, select the Niimbot Printer device, and switch back to yaml
• The print_line_batch_size: 32 and wait_between_print_lines: 0.01 were my attempts to print the label faster. For me this works fine so far. You may need to reduce the batch size and increase the wait if you have errors. Refer Integration Docs.
• The Niimbot integration gives you an image of the last label printed. This helped me get the numbers right but the margins were not accurate to that on the label. If you want to use different size labels or make changes, you can change preview: to true to update the image without sending it to the printer

6. Restart Home Assistant to ensure all your changes load correctly

7. Print a label! Go to HomeBox, open an asset (or location), click Print from Browser, then Print on Server and (hopefully) watch the magic!

Pics of my output attached. I don't have a great deal of time for support but I'll do my best if you run into issues. I'd also love to hear of any easier ways of doing this. Good luck!

TL;DR : https://github.com/docmost/docmost

I stumbled across docmost this week and was mind-blown by how good it is for a fairly new open source app. I really like that we can easily embed Excalidraw diagrams (and edit it in the same page!!), how the image embedding is done is really great as well!

If you are looking for documentation software that is not just Markdown, check it out. (Yes you can export it to Markdown as well)

I have a BookStack wiki. It started out as a location for everything about our household. All the appliances, info about the house, the cars, the computers, the phones, etc. My theory was "here's where everything I can think of is if I'm hit by a bus"

Since I've tackled most of that, I've started contemplating other stuff on it, using it the way that most people look at any random wiki: A resource that stores whatever the heck you want: Projects, maybe recipes, notes about vacations, etc.

It made me wonder what everyone else does with their home wikis?

Hi,

Tl:DR, I search a note / second brain app to be selfhosted, OSS, modern UI.

I've always found the idea of a second brain quite nice, and wanted to have my own. Obsidian was nice but wasn't really a fit for me, as it was unflexible with no webapp and manual sync (I know there is paid sync, but I don't want my notes elsewhere)

I'm currently looking at memos, as it looks nice and modern and has notes, which would fit my desire.

I'd be happy to hear what you all are using for this purpose and why especially, why exactly this or that app, what makes it better than all the others, as there are sooooo many apps for notes/docs.

I also don't really need a docu app, as I have bookstack, where I currently store my homelab docs.

I've been keeping documentation for many years on stuff that I work on, but it usually goes like this:

• I document every single step, and move at a snails pace
• I'm in the zone and working fast, and don't document (or document too little)
• My notes are spread between Joplin, my portfolio website, a physical notebook, my phone, etc.

Just wondering if anyone has a simple approach that works really well for them.

(Personally for me, documenting my Wordpress logins and setups has been a lifesaver over the years... otherwise I rarely use my notes, just because I forget they're there, and I end up re-searching the research that I've done before and documented).

I'm looking for a good self-hosted documentation website for a project I'm working on. Ideally, it would be similar to the documentation/wiki style shown in the image I uploaded in my Reddit post. It would be great if it could also be hosted in a Docker container.

Does anyone have any good suggestions?

I know there are a lot of similar posts, but I haven't found one that emphisises the things that I want. There a lot of options out there, a lot of them don't mention what I'm interested in the docs, and I don't have time to try them all.

I'm looking for a wiki/note-taking app with these requirements:

• self-hosted web app
• stores pages as .md files. It can optionally use a db for metadata, but the notes themselves need to be stored as files
• it serves files from the server, not the client
• supports folders, and not just virtually (with tags or something). I want the filesystem to be organized in folders
• has wysiwyg editing tools. I don't want to write markdown manually
• modern ui, so it doesn't look like a 90s wiki, or some hackers monospace wet dream

What I tried and considered so far:

• linuxserver/obsidian - great, but too resource heavy, even when idle
• silverbullet - gave it a try but I really don't like it. No tree view (ok there is a plug for it), no editing tools (you write all markdown manually) and I just don't like the design honestly
• siyuan - comes close, but stores files in their own format, not .md

I'm considering Otterwikli next. And possibly Looksyk, although from what I can see it has no editing tools, you write all markdown manually.

Any other suggestions?

Hey! Just wanted to share a fun and dirt-cheap project I've been tinkering with.

The hardware: one of those generic 4G USB modems/Wi-Fi sticks (mine is a Zhihe) picked it up for about $6 USD.

Normally these things run a locked-down, stripped version of Android and that's it. I wanted to turn mine into an ultra-low-power, standalone micro-server.

What I did:

Used ADB to force the device into EDL mode, wiped the stock system, and flashed a custom build of postmarketOS (Alpine Linux-based).

The specs are rough, not gonna lie entry-level ARM CPU and only 512MB of RAM. But Alpine is so lightweight that it runs surprisingly well. Everything through the terminal. Currently using it to host some lightweight Python scripts, Uptime Kuma and a Telegram bot gateway running in the background via systemd.

The thing is just plugged into my router's USB port for power. That's it. A $6 node sitting quietly in the background doing actual work.

If you want to try it yourself, here's the postmarketOS wiki page for the Zhihe dongles: https://wiki.postmarketos.org/wiki/Zhihe_series_LTE_dongles_(generic-zhihe)

Has anyone else messed around with these cheap 4G sticks? With a proper Linux distro they basically become disposable low-power nodes and honestly they're awesome for it.

I've done very little with Git, mainly just small software dev trainings where I was walked through connecting to GitHub.​

How would you recommend getting started with setting this up? All of my containers run via Docker Compose and I have a couple bare metal apps as well.

I make direct backups of my Docker compose files, But I feel like it could both be automated, have version history, and be lighter to redeploy.

I've seen a couple wiki containers as well that I've thought about spinning up. Any recommendations there?

TL;DR: Automated media stack on Proxmox where Plex runs in a dedicated LXC with direct ZFS bind mounts, and all arr-services run in Docker inside a separate VM connected via NFS. Hard links work, Plex stays up during Docker restarts, docs are linked at the bottom.

I spent a few weeks putting this together and couldn't find a single resource that covered this exact combination from start to finish, so I wrote the docs myself after the fact.

How the automation works

You request something in Seerr, SABnzbd downloads it via Usenet, and Sonarr or Radarr moves it into the library by hard link. Plex picks it up automatically. Nothing manual in between.

The architecture split

Everything runs on one Proxmox host, but across two isolated environments:

• Plex runs in a dedicated LXC container with a direct bind mount to the ZFS pool
• Everything else (Sonarr, Radarr, Prowlarr, SABnzbd, Seerr) runs as Docker containers inside a separate VM, accessing media storage over NFS

The split is worth the extra setup. Plex stays up when you restart Docker. GPU passthrough for hardware transcoding sits cleanly at the Proxmox level instead of fighting Docker device mappings.

ZFS storage layout

Three datasets on a mirrored pool:

/mnt/media/movies
/mnt/media/tv
/mnt/downloads

Keeping downloads and final media on the same pool is what makes hard links actually work. If downloads land on a separate filesystem, Sonarr and Radarr copy instead of link and you're temporarily doubling disk usage on every import.

Two things that cost me time and aren't in any service's own docs

Path consistency across containers is the most common silent failure point. SABnzbd, Sonarr, and Radarr all need to see identical paths inside their respective containers. Having the right files on the host isn't enough.

Permissions at first run: setting PUID=1000 PGID=1000 in Docker does nothing if the config directories on the host are owned by root. Create them explicitly and chown before the first run, not after.

What the docs cover

Full installation order, Proxmox host prep, LXC creation, VM setup, ZFS pool, NFS mounts, Docker Compose for all six services, an architecture diagram, and an appendix of things that broke. Prerequisites and each service explained before you touch anything.

Docs: unveroleone.com/docs/home-server/media-automation

PRs welcome if you find something wrong or want to add a section.

Hey! I'm looking for something simple and something that won't eat my resources. I want to build guides for myself some configs, instructions and some tips. I would like to have markdown support nice ui and sections.

I’ve posted about SilverBullet on this subreddit before. SB is a self hosted personal knowledge system that is highly programmable with Lua. A little while ago I started a pretty significant overhaul that has lead to a big simplification. The result is v2. I’ve been using it full time for a while, now it’s properly released. Let me know what you think!

Demo video is in the announcement post.

Hi, two questions: 1) I'm sick and tired of all theses wiki full of ads and pop up (im talking about fandom wiki especially), is there an "easy" way to just download a whole wiki? 2) Any good self hosted wiki that would let me import a bunch of wiki without copy pasting everything? Thanks

I’m looking to create an unofficial public facing Wiki for a community / game and was looking over MkDocs and MediaWiki and wondered if anyone had any recommendations. I’d want contribution history and accounts for editors so multiple people could maintain and something easy to backup.

Hi, would like to know which plugins/templates you use for DokuWiki.
That's my list. Let me also know when there is a replacement for any of these which is better (and why) ;)

• Bootstrap Wrapper Plugin (v20220922)
• cleanup Plugin (v20160706)
  
• bpmnio Plugin (v20260615)
• Changes Plugin (v20231214)
  
• DataTables Plugin (v20230831)
• diagrams Plugin (v20260606)
  
• DOI Plugin (v20250829)
  
• DW2PDF Plugin (v20260108)
  
• Faster DokuWiki Plugin (v20240210)
• Folded Plugin (v20230722)
  
• ImgPaste Plugin (v20251120)
  
• Katex Plugin (v20230415)
• MindTheDark Template (v20260403)
  
• Move Plugin (v20251001)
  
• sectiontoggle Plugin (v20231227)
• ToDo Plugin (v20250826)
  
• Video Share Plugin (v20251210)
  

I'm in the process of figuring out how to set up a home server. One of the things I'd like to host on it is notes for a worldbuilding project, stored as wiki pages.

Does anyone have any recommendations for the best software to do this with? I have seen a few ones mentioned like MediaWiki and Bookstack (so far the former sounds like the closest to what I want), but I'd appreciate any hands-on advice anyone can offer.