So I'm in the process of (re-) setting up my homelab and unsure about how to handle databases. Many images require a database, which the docker-compose usually provides inside the stack.

Now my question, shall I have 1 database container which is accessed by all containers? Or shall I have a separate container for each service?

For critical services, which shall have as few dependencies as possible I'm already using sqlite or a similar solution.

Also on a sidenote: I have two docker hosts, can I let the containers of 1 hypervisors use the same internal docker network?

TIA!

So I'm in the process of (re-) setting up my homelab and unsure about how to handle databases. Many images require a database, which the docker-compose usually provides inside the stack.

Now my question, shall I have 1 database container which is accessed by all containers? Or shall I have a separate container for each service?

For critical services, which shall have as few dependencies as possible I'm already using sqlite or a similar solution.

Also on a sidenote: I have two docker hosts, can I let the containers of 1 hypervisors use the same internal docker network?

TIA!

So everyone is talking about cloudflare tunnels and I decided to give it a shot.

However, I find the learning curve quite hard and would really appreciate a short introduction into how they work and how do I set them up…

In my current infrastructure I am running a reverse proxy with SSL and Authentik, but nothing is exposed outside. I access my network via a VPN but would like to try out and consider CF. Might be easier for the family.

How does authentication work? Is it really a secure way to expose internal services?

Thanks!

So I know my way around Linux pretty well. However I never really got the gist of the difference between Snap, Flatpak and Native packages.

What exactly sets them apart?

Why does everyone seem to hate snap?

I have been using all of them, simultaneously on the same system and never really noticed a difference in the way installation, updates etc are handled (syntax ofc).

I hear snap sandboxes? Is that the main reason? Thanks for your insights..

So I know my way around Linux pretty well. However I never really got the gist of the difference between Snap, Flatpak and Native packages.

What exactly sets them apart?

Why does everyone seem to hate snap?

I have been using all of them, simultaneously on the same system and never really noticed a difference in the way installation, updates etc are handled (syntax ofc).

I hear snap sandboxes? Is that the main reason? Thanks for your insights..

I recently upgraded my TrueNAS server to a Synology. While TN has served me well, I don’t have the time anymore to administer it.

I’m now using the opportunity to redo my whole home lab - after years that has become quite a mess.

I’ll retire my old TN appliance as it requires too much energy and is quite bulky. I’m remaining with 1 NUC and a second knock off NUC with slightly lower specs but 2+ LAN ports

What would you do with that Setup? I’ll probably run Proxmox on the NUC and have the second one as a backup, however this one can connect directly to the NAS with a dedicated connection through multiple LAN ports.

I’ll mostly run containers and a few VMs (Git, Pihole, Backup Services, …). My Synology supports both but I’d like to keep things separate. My infrastructure is taken care off, I won’t host pfSense or similar.

I haven’t looked into best practices recently and would like to learn new technologies as Ansible etc.

How do you automate your installations and updates? How does that go together with containers and VMs? Proxmox or maybe plain Debian/Fedora/…?

Thanks for sharing!

A Kremlin spokesman has denied reports that Vladimir Putin has fled Moscow by plane.