GreyBeard

Others have given you a good idea, but since you appear to be using Unifi for switch and firewall, o can give you a clear answer: Don’t set vlan on the Synology. Set it as the “Native” VLAN on the switch port going to the Synology.

Synology can be vlan aware, but you don’t need it. Let the switch do the talking.

On the Synology I recommend putting it on DHCP while you test. Once it starts getting an IP in the right subnet, you can then switch it to static. Just make sure your gateway is right, putting it wrong will cause the device to not be able to reach outside its own subnet.

M365 is doing away with all legacy authentication, do not be surprised if IMAP is completely unusable in the next 12 months. If you simply want to keep a copy of everything, a store and forward SMTP proxy would probably be the solution, so all email going to your domain would hit that first, then send off to M365.

Timers and feed back are useful as well, but you don’t need an app for that, just a simple circuit and a beeper, and maybe some sort of an accelerometer.

The advantage of docker, as I see it for home labs, is keeping things tidy, ensuring compatibility, and easy to manage/backup setup configs, app configs, and app data. It is all very predictable and manageable. I can move my docker compose and data from one host to another in literal seconds. I can, likewise, spin up and down test environments in seconds too. Obviously the whole scaling thing that people love containers for is pointless in a homelab, but many of the things that make it scalable also make it easy to manage.

They may have done a poor job of explains thing, but they are right. Secure boot is a system that every manufactured computer in the last 5+ years has support. The only reason you can install anything but Windows on most PCs is because the manufacturer let you, but they could take it away in an instant by requiring secure boot and only allowing Microsoft’s signatures to boot an OS. Valve could have done the same thing if they chose. That’s basically how the XBox works these days, and it wouldn’t surprise me if the PlayStation is the same, since it is x64 as well.

Nope. It can be cloud if you want it to, but generally, you can host your own controller. I run the controller in a docker container, personally.

I’d suggest looking into the Unifi product line. They have products that meet your needs and then some. I believe the company is based out of the EU so you are likely good in imports.

The problem with WordPress and the like is maintenance. If you don’t keep it up to date, it will get taken by malware. Guaranteed. Any plugins you add increase the risk.

I moved my blog to a markdown based compiled site a long time ago so I didn’t have to worry about that upkeep.

Welcome to Gnome. “The defaults are good so you don’t need customization” seems to he their montra. Honestly there probably is a way to change the sidebar however you like, but it will he buried in a config file and break between upgrades. Dolphin might be a better fit. KDE seems to go the other way, not great defaults, but you can customize as you want.

So I setup every “client” to have the “server” as the introducer and auto-accept shares. Then on the “server”, I add the new client, and give it all the shares. The new device auto accepts, and all the other clients automatically include the new client.

I may be misunderstanding what you want, but the introducer feature seems to solve the problem. You setup your “server” as the introducer for all your other devices, then when you add a device, you just setup your new device with the server, and all other devices get the trust of the new device from the server.

Completely unrelated: A feature that server likely has that you should investigate is called “iDRAC”. There is probably a dedicated NIC on the back for it. It allows you to power on the server, control most “BIOS” features, and see the screen remotely.