Ode to Fargo Publisher
by Frank McPherson Friday, July 28, 2017

I moved my instance of Fargo Publisher to Google Cloud Platform. The process was pretty straight forward except that I had to work around an issue caused because Nodejs doesn't have access to port 80. 

One of the interesting things about Fargo Publisher is that it does not store any data on the server in which it runs and it provides a CNAME-like functionality by mapping URLs to a folder structure. What this means is that there isn't much to configuring Fargo Publisher beyond storing the bucket name and associated directories, along with Amazon AWS credentials.

I am no longer using Fargo for my blogs, but I did want to provide access to what I had written using it. The provider I had been using to host Fargo Publisher has become very unreliable, and so I decided to move it to Google Cloud Platform. (Btw, Dropbox still has not turned off their old API and therefore Fargo still works with it. Who knows for how long?)

The first post I wrote using Fargo was on March 19, 2014 and the last one of substance was on October 10, 2016. All in all, a pretty good run.