If it works for you, there is no reason to switch.

The benefit for me is mostly the systemd integration (e.g. do a simple DB backup before running the container using StartExecPre) & the corresponding unified logging with journalctl. Then there is auto update and boot persistence without having to run an additional process.

The hardest part for me was to switch from docker compose to quadlets, but there is podlet to help with the conversion.

https://github.com/containers/podlet

Thanks for the suggestions, but no, I have not. I am not looking to replace my mail app, but to remove it from my phone/desktop entirely and instead running something similiar on a server, so I can access it from my phone/desktop when needed.

Thank you, this definitely goes into the right direction and I will check them out!

but then you’d still have to have your mobile mail client go and download all this mail you said is a battery drain, so you’re sort of negating yourself.

That is precisely my point. I do not want a mobile or desktop client anymore. Just send a client which is running on a system which is always running anyway to send me a notification and I can then decide if I will check it out now or if it can wait.

Proprietary mobile clients often work similarly, they do the “heavy lifting” on the server side, send a notification, but only temporarily load the mails you explicitly view temporarily on the device. And thus, they use less battery and storage of the device. Another benefit for the unified client would be faster sync of mail status (e.g. read/unread) as it is only one client on the IMAP server instead of one on each device. And another benefit would be not having to migrate email clients when replacing devices.

transphobia

The what now😐

Totally possible:

https://beszel.dev/guide/additional-disks

Beszel. Probably the easiest tool of all the mentioned in this thread.

https://github.com/henrygd/beszel

That being said if youre looking for performance, the last thing you’d want is open source nvidia drivers; theyre built entirely off reverse engineering, which takes time.

Pretty sure that is not true anymore since a couple of years. Only newer cards can capitalise the gains from the ‘official’ open drivers though.

https://developer.nvidia.com/blog/nvidia-transitions-fully-towards-open-source-gpu-kernel-modules/

Depends on what you want to play. If you want to play current games with current hardware then current kernel and drivers help a lot. A base Debian would (if it even works) probably less FPS than an current gaming distro.

Backed this on Kickstarter. Seems honestly too good to be true, so I am antsy to get my hands on it.

• monitors CPU, memory and disk space
• can accept multiple hosts to watch
• has some sort of alerting system
• can be deployed as a single docker container
• can be configured using a text file
• configs can be imported and exported inside the docker compose file

https://github.com/henrygd/beszel

There is no really config to speak of. You setup the hub. Then you click on add system and write in the IP. Then you click on “Copy compose”. That is the agent you can then deploy with a compose file on any system. Click on add and it is there.

The only thing you might want to configure is alerting, but only once on the hub.