GL.Inet products that use Mediatek chipsets are great since you can usually flash standard OpenWRT on them. I would avoid routers with different chipsets since they are unlikely to get proper support.
(Though I can’t say that my MT-6000 is cheap, but it is an extremely capable router. That is top of the line though, they have cheaper stuff.)
I would go back to your CAD model and tweak it for better printability. If it was a model you downloaded and without a source CAD model I would just remodel it myself to be more printable.
The solution is to not use Http based validation of the cert, but use dns based validation. Possibly combined with a wildcard cert for your whole domain. This is what I do for internal services on my LAN, along with split DNS so that the internal services aren’t even listed in public DNS.
What is that log analysis tool you are using in the picture? Looks pretty neat.
It is common custom to indicate quotes, with either “quotes” or for a longer quote a
block quote
The latter can be done by prefixing the line with a here on lemmy (uses the common markdown syntax).
Doing either of this help avoid ambiguity.
Agreed, I run arch on my desktop and laptop, because it is more stable (in the sense of fewer bugs, things like suspend/resume works reliably for example) than any other distro I have used.
But on my VPS and my Pi I run Debian because it is more stable (in the sense of fewer upgrades that could break things). I can enable unattended upgrades there, which I would never do on my Arch system (though it is incredibly rare for those to break).
Also: if someone said they were a (self proclaimed) “semi noob” I would not recommend Arch. I have used Linux since 2002, and as my main OS since 2006. (Furthermore I’m a software developer in C/C++/Rust.) While Arch is a great distro, don’t start with Arch.
While that works, it will use more electricity than an all-in-one ARM based router. Depending on prices and renewable/fossil mixture where you live, this may or may not be a concern.