thomas

joined 1 year ago
[–] thomas@lemmy.zell-mbc.com 1 points 10 months ago

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.

[–] thomas@lemmy.zell-mbc.com 18 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] thomas@lemmy.zell-mbc.com 1 points 1 year ago* (last edited 1 year ago) (2 children)

:-)

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? :-)

[–] thomas@lemmy.zell-mbc.com 2 points 1 year ago (4 children)

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.

 

Proxmox Backup Server 3.0 available

It's based on Debian 12 "Bookworm", but uses the newer Linux kernel 6.2, and includes ZFS 2.1.12.

  • Debian 12, with a newer Linux kernel 6.2
  • ZFS 2.1.12
  • Additional text-based user interface (TUI) for the installer ISO
  • Many improvements for tape handling
  • Sync jobs: “transfer-last” parameter for more flexibility

Release notes
https://pbs.proxmox.com/wiki/index.php/Roadmap

Press release
https://www.proxmox.com/en/news/press-releases/