You would expose the port to your host which makes the db acessible by anything running on the host, docker or native. Something like

`port

• 5432:5432 `

But I would recommend running a dedicated db for each service. At least that's what I do.

• Simpler setup and therefore less error-prone
• More secure because the db's don't need to be exposed
• Easier to manage because I can independently upgrade, backup, move

Isn't the point about containers that you keep things which depend on each other together, eliminating dependencies? A single db would be a unecessary dependency in my view. What if one service requires a new version of MySQL, and another one does not yet support the new version?

I also run all my databases via a bind mount

`volume

• ./data:/etc/postgres/data...`

and each service in it's own directory. E.g. /opt/docker/nextcloud

That way I have everything which makes up a service contained in one folder. Easy to backup/restore, easy to move, and not the least, clean.

Let me throw in Paperless NGX, https://github.com/paperless-ngx/paperless-ngx

Like you I have OPNsense in a VM on one of my PVEs. But I only made sure the nigthly VM back up ran and didnt even bother shutting down the VMs during the upgrade. The VMs got restarted during the final reboot, as the would with every other reboot, and I was back in business.

I herewith grant you the official title of a real hacker :-)

That's the tool I was looking for, thanks a lot!

Turns out there are no more http websites out there, at least I couldn't find any. Good for our security, bad for my demo :-)

Wireshark is my backup plan for a text based demo. Unless I am missing something pictures in Wireshark will just be binary stuff across multiple packets which won't work for a demo. The tool I am looking for managed to identify which packets contains image data and showed them in a grid

I run this one for a few months now: https://github.com/techsneeze/dmarcts-report-parser

I did indeed, and I have to say I am impressed from what I see so far! A really nice and complete tool you created. Thanks a lot for putting in the hours 👍

Here's my little list:

Proxmox VE 1

1. OpnSense (VM)
   • Wireguard
   • Unbound
2. PiHole (LXE)

Proxmox VE 2

1. Dockerhost (LXE)

• Nextcloud
• Akkoma
• Lemmy
• Synapse
• Keycloak
• Dashy
• Paperless NGX
• Whoogle
• Grafana
• CCU Historian
• DMARC / TLS Reports
• Prometheus

RaspberryMatic Octoprint

eMail

• Postfix, Dovecot, etc.
• Ciphermail email encryption

Well, depends on what your client OS is I guess. There's a cli tool called proxmox-backup-client which allows you to back up OS level, I use this to back up the host OS of my PVE server. I am not sure if this tool is available for Windows/Mac though.

I have 2 PVE servers and on one I have installed PBS in parallel, which works fine. Just a different port to get to the UI: PVE: https://pve2:8006 PBS: https://pve2:8007

KeePassXC for me…

KeePassXC and Nextloud to sync things between devices…

I used this guide when setting up my self hosted email: https://workaround.org/ispmail/buster/big-picture/

I also added in Ciphermail for email encryption and it's been almost hands off ever since.

Granted, there were quite a few things to digest until things were working as I wanted.

I just sort of finished setting mine up, so not really experienced. But I am using the pre-compiled image instead of building it locally. Did you try building it directly with "#docker build…" instead of "docker-compose up"?

For me it's Borg backup for Nextcloud an all the other servers

:-)

But seriously, I was wondering about the requirement to shutdown the VM's and couldn't come up with a solid reason? I mean, even if QEMU/KVM/Kernel get replaced during a version upgrade or a more common update, all of these kick in only after the reboot? And how's me shutting down VMs manually different from the OS shutting down during a reboot?

I know I am speculating and may not have the fill picture, probably a question for the Proxmox team, there may be some corner case where this is indeed important.

By the way, Mexican or US black strat? :-)

This may be a long shot, but it's what I do, so it might be an option: Set up a crypto gateway like CipherMail which will automatically decrypt inbound email and sign/encrypt outbound. The result is that your Thunderbird will never get to see an encrypted email, decryption is handled transparently before it hit's your inbox. Obviously, if you don't trust your email provider, this is not an option.

This isn't simple and hence not for everyone, also comes with dependencies on your email provider, but it works flawless for me ever since I set it up. I run my own email server, hence adding in CipherMail wasn't a big deal.

I arrived at the same conclusion. Been trying to connect from my Akkoma account but like you, figured out this doesn't make a lot of sense. So here I am, posting from my 2 hour old Lemmy server :-)

<<so I don’t want to install the nginx container in the sample compose either>> Thought the same initially but it turned out both nginx instances are required. I have a working setup with an installed nginx instance + certbot and an almost unmodified docker-compose.yml The modifications I made were changing container names (so they fit my standard) and the http port

The lemmy documentation https://join-lemmy.org/docs/administration/install_docker.html recommends the following location block for the installed nginx:

  location / {
       proxy_pass http://localhost:LEMMY_PORT;
       proxy_set_header Host $host;
       include proxy_params;
}

This did not work for me! I had to comment the proxy_set_header line to make things work. With it I run into an error 400.

I see that @stulli recomends the gutmensch docker-compose repo. That repo is using the techsneeze repos I mentioned above, in fact I use the gutmensch docker setup as well. Maybe you are also interested in a pull request in the techsneeze repo which adds support for TLS reports. It's sitting there for months but for some reason doesn't get merged. But it works just fine for me and others which commented on the pull request. I ended up forking the techsneeze repos and applying the merge request on my fork…

By the way, I wasn't able to respond to @stullis cooment because somehow his comment didn't get federated to my Lemmy instance, teething problems I guess :-)