PlexSheep

Hosting email with mailcow dockerized worked pretty good on my netcup vps, but before you go into hosting email ask yourself a few questions:

• Will you use your selfhosted mail for important things? (Banking, official correspondence and so on)
• Can you promise a near 100% uptime? Otherwise, some email might not reach you.
• How important is the Mail you send? Some (stupid) Blocklists generally block all IP ranges that are sold out by vps companies and other kinds of IAAS.
• If you register any accounts with your selfhosted mail, can you guarantee yourself that your email account is secure? Don't underestimate what an attacker can do with a compromised Mail account.

I personally ended up scrapping my email server eventually. Nowadays I pay a company to do the mail hosting, you just need to set some DNS records and they do everything else. Personally, I'm with proton, but there are many good alternatives.

I've never had problems with appimage, and for me, containers are for my servers. I don't want stateless, sandboxed applications for my workstations.

In what ways is it broken?

You can use this desktop file.

Add desktop files like this. Be encouraged to search the web for solutions on your own :)

Appimage is better for cli apps. Different purposes. Neovim appimage is very useful

Im a selfhosted, git an older desktop that I use as my homeserver with some hdds in it, combined into a combined refund and storage with btrfs.

No, you'd have to add a desktop file

For me personally, it doesnt load my configs. So better use appimage

Haven't gotten to try yet, will do

The config for modern neovim users mainly consists of plugins and configs for plugins.

Nvchad is a ready made neovim config, that can be extended, not just a plugin.

I'm a heavy neovim user, also using Linux mint. I use the app image from the GitHub release page. Sure it means having it not automated, but that's fine with me.

Basically download the appimage, make it executable with chmod +x and move it to a location in your PATH, line ~/.local/bin/nvim (nvim being the name of the file, add that to your path. Another popular location might be /usr/local/bin/nvim). Afterwards, you can just use nvim in your terminal.

That's by far not the latest version. The current prerelease is on v0.10