Alternatively, you can create new users from the command line.
This can be done as follows:

If synapse was installed via pip, activate the virtualenv as follows (if Synapse was installed via a prebuilt package, register_new_matrix_user should already be on the search path):

cd ~/synapse
source env/bin/activate
synctl start # if not already running
Run the following command:
register_new_matrix_user -c homeserver.yaml
This will prompt you to add details for the new user, and will then connect to the running Synapse to create the new user. For example:

New user localpart: erikj
Password:
Confirm password:
Make admin [no]:
Success!

This process uses a setting registration_shared_secret, which is shared between Synapse itself and the register_new_matrix_user script.
It doesn’t matter what it is (a random value is generated by --generate-config), but it should be kept secret, as anyone with knowledge of it can register users, including admin accounts, on your server even if enable_registration is false.

https://element-hq.github.io/synapse/latest/setup/installation.html

OpenWrt with 802.11r and 802.11s configured will work as a mesh network with roaming functionality.
https://openwrt.org/docs/guide-user/network/wifi/mesh/80211s
https://openwrt.org/docs/guide-user/network/wifi/roaming

Not many Ruckus devices that are supported though:

Brand - Model - Supported Version
Ruckus - ZF7025 - 23.05.2
Ruckus - ZF7321 - 23.05.2
Ruckus - ZF7341 - 23.05.2
Ruckus - ZF7343 - 23.05.2
Ruckus - ZF7351 - 23.05.2
Ruckus - ZF7352 - 23.05.2
Ruckus - ZF7363 - 23.05.2
Ruckus - ZF7372 - 23.05.2

https://openwrt.org/toh/start?toh.filter.supportedcurrentrel=22.03|23.05

Software: OpenWrt - https://openwrt.org/docs/guide-user/network/wifi/roaming
Devices: Supported devices found here - https://openwrt.org/toh/start?toh.filter.supportedcurrentrel=22.03|23.05

pfsense and opnsense are very similar. The pfsense devs has acted like jackasses towards the opnsense gang. They are both great for a router/firewall/vpn device. I would use external access points with them.
I think there are more addons to pfsense than opnsense.

OpenWrt is great when it comes to WiFi, but I find it much less intuitive to use for router/firewall parts. Could be that I am used to the way pfsense and opnsense do things.

Neither do switching from what I know, so pair the router with a switch of your choice.

I’m so happy I went with a self-hosted Forgejo for my code repo.

Gonna check it out!
Is it easy to setup automatic responses to the alerts, f.e. restarting a service if it isn’t answering requests in a timely manner?
Have you used it together with Windows Servers too?

I’ve used SNMP a lot together with nagios so I should be able to handle it. :D

I’ll have a look! Cheers!

Cheers! I’ve heard of Prometheus/Grafana but VictoriaMetrics was a new one. Gonna look into it!

For signal I imagine you’ll find the best answers here:
https://github.com/signalapp/Signal-Android/blob/main/CONTRIBUTING.md
https://community.signalusers.org/c/development/android-development/22

" in" appears 25 times on the page to be exact, with 16 of those being in the table of contents and 9 being in the text afterwards.
“in” appears 54 times, as you know end up hitting “string” and so on.

Had I known that the functions table of contents was as short as it is I would probably have just scrolled.

After which ctrl+f " in" takes you to the correct chapters. I do agree that a direct link would be more helpful.
And for learning postgresql I agree it isn’t very helpful - using their tutorial links, w3schools or something like udemy if you prefer video format is the way to go in that use case.

I remember back when you were told to learn to work with the documentation, not memorize it, because you will always have access to it as a reference. Maybe bookmarking reference books/documentation will make a come back as the search engines degrade.

Your result returns version 9.0 that went EOL 2021, same as Googles fourth result in OP.
nvm, second result is correct.

I definitely feel the pain when it comes to worthless results nowadays. Though in this case DDG comes through:

Adding documentation to the search makes the “correct” page soar to the top:

I consider client devices to be a big risk factor and if I can keep them from having direct access to the Backup NAS and the IoT I consider that a big win. A simple ransomware attack on a client device would find any NFS/SMB shares the client can access and start encrypting - having the Backup NAS on a separate VLAN that only the server can access stops most of those from affecting the backup and makes restoring a lot easier. I would definitely recommend having an offline backup of the NAS as well in case of the server being breached.

I agree with this, protecting everything behind a VPN is the way to go. I help friends setup their vpn client to my stuff if I want them to access an internal service.

If you go for SSD another thing to think about is the TBW on them. Buying a low endurance SSD might save some electricity but will cost more in SSDs over time. Example:
Crucial P3 Plus M.2 NVMe SSD 2TB (2.67W on your link) has 440TBW compared to Kingston Fury Renegade M.2 NVMe SSD Gen 4 2TB (4.92W on your link) with 2000TBW.
Those few watts you save on using the Crucial P3 Plus will be less than the extra cost in buying new SSDs earlier.
The site I checked TBW on has the Kingston Fury at $9.4 more than the Crucial P3 Plus.

I think proper datacenter 3.5’’ HDDs will give you the most efficient Wattage per TB disk space
Seagate Exos X20 Harddisk ST20000NM007D 20TB SATA-600 7200rpm is supposed to have
Power Consumption 5.4 Watt (idle) | 9.4 Watt (random read) | 6.4 Watt (random write)

Regarding management UIs I’m a fan of Cockpit (https://github.com/cockpit-project/cockpit https://cockpit-project.org/)

Regarding management UIs for docker I believe most use either portainer (https://github.com/portainer/portainer https://www.portainer.io/) or dockge (https://github.com/louislam/dockge https://dockge.kuma.pet/).

Regarding Samba most NAS devices simplify it a lot, but it isn’t that complicated to do on Fedora either and once you’ve got it setup it’s not gonna need a lot of tinkering. (https://docs.fedoraproject.org/en-US/quick-docs/samba/)

Whether you invest in a NAS or not I recommend you invest in a USB disk large enough to act as a backup for the storage disks. That’s not an investment for later but one you want right away. And do make certain it takes backups, not replicates data. A popular option is Borg Backup (https://github.com/borgbackup/borg https://www.borgbackup.org/)
If I went for a NAS I would Borg Backup the laptop to the NAS and then use the NAS own backup software to backup to the USB.

If you liveboot Fedora or something with USB - how’s the upload then?
Should be a quick way to determine if it’s software or hardware based.

edit - Seems that others have had upload troubles with latest Proxmox and fixed it by downgrading:
https://old.reddit.com/r/Proxmox/comments/19d0bf7/slow_upstream_thru_proxmox81/

So… no need for a DE :)

No real need for me to remove it either, but your point stands. :)