If you need another thing to do, you could try to make your opnsense HA and never have your internet stop working while rebooting a node. It’s pretty simple to set up, you might finish it in 1-2 evenings. Happy clustering!
If you need another thing to do, you could try to make your opnsense HA and never have your internet stop working while rebooting a node. It’s pretty simple to set up, you might finish it in 1-2 evenings. Happy clustering!
I know, but every time I had to do that it felt like it’s a jank solution. If you have a raspberry pi or smth like that you can also set it up as a qdevice.
…and if you’re completely fine with how it is you can also just leave it like it is
You should get another node, otherwise when node1 fails node2 will reboot itself and then do nothing because it has no quorum
Switch to SearxNG instead
Arent SR modules okay for your run length? It doesn’t look like you have >300m (ca. 2 football fields if you are american) from your rack to your office
If you update your OS, it could happen that a changed dependency breaks your app. This wouldn’t happen with docker, as every dependency is shipped with the application in the container.