💾 Archived View for going-flying.com › ~mernisse › 25.gmi captured on 2022-04-29 at 11:15:15. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-04-28)
-=-=-=-=-=-=-
I was browsing recent items on Antenna[1] recently and came across a couple replies to JDJ's[2] question about self hosting. I have found the label a bit odd since I came across it a few years ago since I've run public services on systems dating back to when all I had was a 14400kbps demand-dial connection and unless you were a business or a school you hosted services yourself.
With that much history as you may expect the answer is a bit complex. You may be best served by looking at the network overview page on my website[3] for some more information but here we go.
gemini://warmedal.se/~antenna/
gemini://ew.srht.site/en/2022/20220319-re-self-hosting.gmi
https://www.going-flying.com/network.html
I used to run things out of my house but gave that up at some point in the early 2000's. I have a combination of cloud servers that provide geographic redundancy for a physical server at a colocation facility that does most of the heavy lifting. Internal services are served from the house but they are exposed to the Internet via a layer 3 VPN link to the colocation facility.
There are many applications running, of which many are bespoke creations. Everything is tended to by either Puppet or Ansible these days because I'm growing less interested in the day to day in my advancing age. Authentication is handled by an LDAP database that is replicated to multiple sites. I have an internal multi-level certificate authority that issues certificates for clients and servers and is automatically trusted. Telemetry and health data is collected by collectd and sent to InfluxDB to be processed by Grafana. This includes my bespoke 915MHz sensor network. There is a mariadb (nee mysql) and postgres database server for applications that need them.
🚀 © MMXX-MMXXII matt@going-flying.com