But you are 20 versions each with breaking changes behind…

It is that simple. Make the dns entry point to your vpn subnet 10.10.100.X. The way it works is anyone not on your vpn won’t be able to resolve the ip address and will get an error. Anyone on the vpn will be able to resolve the ip address and connect via the vpn connection.

The part people are talking about that is likely confusing you is that if your service is already available via your actual ip address 1.2.3.4 then you have a security concern since anyone can access 1.2.3.4 even without your domain name pointing there. They are encouraging you to make sure your 1.2.3.4 network doesn’t allow access but updating your firewall settings to make sure it blocks connections that are not made via your vpn subnet of 10.10.100.X

Yeah I think that would give me essentially the same access that I have now but through a GUI. I’m hoping for something that will cram my logs into a data store of some sort and present them on a GUI with search, filter, aggregations, etc…

In this analogy, GitHub would be the library and the awesome list would be the recommended by the librarian section. If my librarian stopped curating that section and just filled it with a specific type of book no matter the quality I would stop browsing their curated section.

I miss the days when awesome lists were curated to actually have awesome stuff instead of being a list of 250+ self hostable apps.

There is no way these are all awesome. Call it the giant list of self hosted apps or something that actually makes sense.

Definitely! I’ve used them for years and they are super convenient. Especially in small space living. I have a small server setup in a closet that is a direct attached raid array with an m1 Mac and an Intel nuc on top.

In general I prefer the max because it can do a lot with very minimal heat generation but using a Mac mini as a server has a few downsides that you won’t run into with a nuc. Things like arm vs x86, no way to run the OS headless, cost, etc…