The usual go to for self hosted password managers is VaultWarden. There’s no deb or rpm package but you can get it spun up with docker pretty easily. Any reason you’re specifically looking for “included” or packaged solutions? That’s going to severely limit your options.
I have a single Proxmox host running:
There’s a bit to explain here. So the root user is basically the equivalent of Administrator. One big difference (there are many) is that when you run something as root using sudo, you are actually running as the root user. When you ran the first command to create the folder, you created it in your home directory using the ~ shorthand variable which points to your /home/ user folder. The second command, also references your home folder. However since your running as root, it’s looking for the file in the root user’s home directory or /root, not your home folder.
The config file needs to be in the home directory of the user running the command unless you can put the full path to the config file in the command, then you can put it wherever you want.
Not weird at all. All my data is shared from a single VM but I access it from several others than run jellyfin and the *arrs, and a few other things. When you don’t want everything running on the same virtual machine, you need to share the data over the network, even if it’s all on the same physical box.
If you want multiple containers or VMs to have access to the data it needs to be shared from somewhere. As others have mentioned you can setup a VM to run a NAS OS like FreeNAS or just run a container with samba and pass the drive through to the container. The difference is how you access the data from the other containers and VMs. You’ll access them via samba shares as opposed to local drives.
To my knowledge two containers/VMs cannot share the same physical or virtual disks in Proxmox. I tried and had to go a different route to get what I needed.
I don’t know enough about the fediverse or Lemmy code to say how easy or hard this would be to implement but if we’re logging in with the username noogs@lemmy.noogs.me for example, it’s reasonable for the app to assume the server is located at lemmy.noogs.me and it can derive the likely URL of https://lemmy.noogs.me from that. The only case this wouldn’t work is if your instance is running on a port other than 443 because then we need some way to tell the app what the port should be.
Email (or at least Microsoft Exchange email) uses a protocol called autodiscover for this which uses DNS to tell an email client where to get connection information from, it then polls that URL for the information and configures the email client automatically. Using a similar DNS based approach may be useful as well.