I run a supermicro chassis with 6 3TB drives in a RAID6 using a dedicated hardware RAID controller. Old school for these days but works for my needs for now. Drives were free from a buddy of mine so until they start dying or I need more space, they’ll do. Then I have two 120GB intel enterprise SSDs for running Proxmox. VMs and LXCs are all on the spinning disks which surprisingly perform well enough.
I run a supermicro chassis with 6 3TB drives in a RAID6 using a dedicated hardware RAID controller. Old school for these days but works for my needs for now. Drives were free from a buddy of mine so until they start dying or I need more space, they’ll do. Then I have two 120GB intel enterprise SSDs for running Proxmox. VMs and LXCs are all on the spinning disks which surprisingly perform well enough.
I run a supermicro chassis with 6 3TB drives in a RAID6 using a dedicated hardware RAID controller. Old school for these days but works for my needs for now. Drives were free from a buddy of mine so until they start dying or I need more space, they’ll do. Then I have two 120GB intel enterprise SSDs for running Proxmox. VMs and LXCs are all on the spinning disks which surprisingly perform well enough.
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.
This is the way. I’m routed through cloudflare with private registration as well. The exposed IPs belong to Cloudflare and only they and I know where it goes after that.
Ah ok. So the only thing left behind really is your name which again I suppose could cause problems out in the ActivityPub world but that’s way too deep into the development of Lemmy for me so I’m only speculating. Basically my random theory is if @[email protected] is somehow tied to a particular instance ID and now that instance ID is different, I’m not sure how ActivityPub handles that or if that even matters.
Did you purge your database when you destroyed the old instance? I’m not sure how Lemmy handles instances and databases under the hood but I suppose a database from a different instance might cause problems.
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.