Here's how this site is currently setup

- Single Linux server running in Google Compute US-East.
- The Google Compute instance started as an "n1-standard-1".  I've added additional memory but have stuck with a single CPU.
- The only things installed in addition to the base OS are Git and Docker
- Dockerfiles and scripts to manage all of the containers are stored in a private git repo
- Backups consist of a snapshot in GCP and tarballs of data copied to Google Drive or downloaded locally.

This setup works pretty well and makes the whole thing pretty portable.  I had originally built all of this is US-Central but later decided to move it to US-East.  It was a pretty simple task of creating a new instance, installing git and docker, pulling the docker repo, copying the data into place, then creating the containers.

For non-web things, like my son's minecraft server, they just run as a container and answer on their native ports.  I've created my own Docker container for minecraft which can be found here:

For web sites and things that need to answer on tcp/80 & 443, I'm using Nginx as an HA Proxy which is doing SSL termination.  Nginx is configured for all of the sites and serves some static content as well as proxying to the various containers.  For example, Nginx listens on tcp/80 & 443 for this site.  If it receives a tcp/80 request is redirects to tcp/443.  When the tcp/443 session is initiated, Nginx proxy's the request to the internal IP of the NK4I web container on tcp/8080.  For another site, it might be tcp/8081.  Within the Docker container configuration, Docker handles translating the tcp/8080 back to the native tcp/80 of the container.  This way ports aren't altered for the applications themselves.  And the mappings are easily seen when you look at your running container list.

To do an update/patch, I pull the latest container version and update by "create" script in the repo.  Stop the container, remove it, and run the create script.

So, I'm able to run a minecraft server, 3 different CMS' for different web sites, some static HTML content, and a database to back-end the various CMS'.  All of this on a single CPU (runs about 15% continuous and about 80% when my son and his friends are playing minecraft) instance with 5.5GB of memory.

Wow, how time flies...  Yet again...

It's been about a year since anything worthwhile has been added here.  But a lot has changed.  The 2 SOTA activations happened as part of a trip to TN.  Since that trip, we've moved to the greater Knoxville TN area, sold our house in Summerville SC, bought just over 15 acres in TN, and are working at building a house.

Over the course of the year, I've kept this site up-to-date with patches and it's been migrated around a little from a private server at my home to being hosted in Azure and then finally in Google Compute.  I'll do a whole article on the back-end as it's a rather fun solution.

Winter is almost here and the leaves are falling.  Time to get up onto a mountain and do a SOTA activation.

After a bit of neglect, I've updated the underlying software and moved the site to a different server with a bit better performance.  Now, to create content...


SOTA activation of W4C/US-001 on June 24, 2016

Sassafras Plaque

I was traveling back home and took a short break to activate Sassafras Mountain.  The drive up to the base of the summit was easy and there's a very nice parking area.  There's access to the Foothills Trail as well, so there's a good amount of foot traffic across the summit.

Most of the summit has been cleared as part of a project to build an observation tower.  I found a sheltered spot on one of the small logging roads they've cut into the deadfall.

Station was my KX3+PX3 and the 33' Jackite pole with the end fed half wave antenna.  All of it running from my new Bioenno LifePO4 battery.

Thanks to KW4JM, KB1RJD, KB1RJC, W0MNA, W4KRN, KI4SVM, KC3ABF, VA2MO, and VE2JCM for making contacts.

On this activation I had 2 summit to summit contacts, KW4JM on W4C/WM-027 and KI4SVM on W4C/CM-009.