Currently I have one Docker host. I want to split my containers across 2 hosts. Both just small form factor PCs. (Lenovo, forget the exact model. But each have 16gb of DDR4 and an i5. One is 8th gen, and the other I have to double check. The one I haven’t setup yet has an Nvidia card of sorts. I want to offload media services onto that one.)

Anyways, on to the breakdown:

Containers:

• Technitium (DNS)
• DNSWeaver (DNS from Labels)
• Caddy (with custom plugins Caddy-Docker-Proxy mainly)
• WG-Easy (Wireguard VPN)
• DDNS container
• Authentik (SSO Provider)
• Signal-CLI
• Molly Socket
• Multiple Docker Socket Proxy containers
• SearXNG
• Uptime Kuma
• Vaultwarden
• WUD
• Speedtest Tracker
• Dozzle
• Forgejo
• FMD (Find my device)
• Bookstack
• Syncthing
• Vikunja (Kanban board)
• Navidrome
• Maloja
• Audiomuse
• Doku
• Jellyfin
• FreshRSS
• Nextcloud
• beets
• Komga
• Lyrica (with some custom scripting to search my music for matching LRC files)
• Homepage
• Ntfy

Next up I want to add Autokuma. However, I am going to split these containers onto another machine yet.

The joke with my comment was that you give little to no context. For better advice and help giving some context may be beneficial.

Have you tried scribble scrabbling the florpimijig while connected to your schmoopy doo?

I use a Motu M4 audio interface with headphones wired to it, as well as a Shure mic. Since I do music I already had it setup.

Just set this up myself. Its quite nice

Not an apple user in any definition but glad apple users are getting clients for Navidrome too. I love Navidrome, especially paired with Feishin for desktop; Symfonium or Tempus on Android

Passbolt pales in comparison. The fact I can only get the android app from google play. No thanks. That is a deal breaker right there. I am working towards moving 100% off from google play.

After quickly spinning up a container of it; it feels very unpolished and can’t say it will replace Bitwarden/Vaultwarden for me.

I quite like Bookstack. The next step to my documentation journey is auto-uploading README.generated.md files that are generated by a script running on a timer triggering a service with systemd.

Though this doesn’t cover my physical machines in production.

I have it setup similarly currently /root_compose_dir/stack_name/compose.yml

But I’m taking a step further, ans using labels to generate README files. And will automate putting it into my bookstack

I am taking a similar philosophical approach.

I’m lazy too, so I am working on havinf most docker documentation automated…

If I have to do it more than once, automated.

I am leaning that way too. Although I do want to maintain a wiki that I can host.

So I settled on using a script that runs as a service on a timer, and can beanually triggered to generate README.md files that get synced with my git repo of docker containers

This will be huge for me, as most of what I run are containers.

The next step will be using Bookstack’s API to push these README.md files into books on my bookstack container.

I’ll go a step further and setup automated exports of these documents.

Wasn’t there when I posted this comment. But thanks

Thank you!

I dont but I am interestes in learning something new

I am taking precautions to have my setup easily deployable no matter the hardware. The only real documentation becomes mountpoints and such for external storage.

For DNS and Reverse Proxy entries, I have those automated. Any time I spin up a new docker container, that information is deployed with labels. Also entries into my homepage.

The .env files contain any variable I would want to store to make my setup portable, shareable and not have to worry about leaking any of my information. Not that it would be end of the world considering nothing really leaves my network unless it is through my VPN.

I am of that camp, lazy, when it comes to documentation. I have lucked out, as of now after years most if not all of what I need setup has been kept in the ol noggin. But I am building out documentation as we speak. Slowly but surely.

I do like the README.md approach.

Well, this de-incentivizes me from even trying this out. Thank you for sharing!

This greatly interest me. I may check this out.

Is there ways to Automate Kid3? Or is it strictly user intervention?

Always happy to share!

Right now I have 53 containers going on a box with 16gb of ram, and an 8th gen i5.