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.

Thanks for the response. Seems like I made a good choice by going with the AGPL

Dumb question because I’m not fluent in License-Lore: which license would be best at preventing others (or me from the future) from selling / closing down the licensed work? Would it be GPL, AGPL, MPL, something else?

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

i can’t believe so many people didn’t get that part

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

My brother in Christ, how would one confuse a VM with an LXC in Proxmox? They couldn’t be more clearly labelled as different things than they already are. But don’t let this distract you from the fact that in 1998, The Undertaker threw Mankind off Hell In A Cell, and plummeted 16 ft through an announcer’s table.

Why not use both? I have PVE installed on all of my hosts and then use k3s/docker in VMs. If there ever is anything you don’t want to or just can’t deploy as a container (e.g. opnsense, hassio, truenas, windows [for whatever reason you might have]), you can just spin it up as a VM and not worry about adding and maintaining another physical machine