v0.90 -- New item in the httpLog.json file, the number of seconds it took to process the request. Using this to monitor the server to see if increased traffic is causing it to slow down.
v0.89 -- if we're not redirecting, and the path ends with "/", get index.html. Pretty standard server stuff.
v.088 implements a new configuration option, whether you want Publisher to redirect to the content stored on S3 or serve it directly.
v0.87 implements the getenclosureinfo endpoint. It takes a URL as a parameter, and returns the length and type of the file it points to. This is used in creating the <enclosure> elements in RSS feeds.
v0.86 implements the httpurlschanged enpoint. It gets a set of URLs and returns the dates when they last changed. Used in the Fargo for Workgroups feature.
Version 0.85 implements hits-all-time and hits-today, and rolls over the date at midnight GMT.
Version 0.84 does a reverse DNS lookup on the client IP address. However it doesn't yield much useful info, as you can see from my httpLog file.
Version 0.83 fixes bugs added in 0.82. Hardened the server, so it reports its own errors in the log file instead of crashing.
Version 0.82. Maintain a new stats file, httpLog.json.
Version 0.81. Fixed a bug where redirects would recurse indefinitely.
Version 0.80. Two new API endpoints, one that returns server status in JSON, for monitoring apps and one that does an HTTP request for Fargo running in the browser.
Updated publisher to version 0.79. Now it redirects to user sites if you point the domain at the server.
Heroku How To: Get your own Fargo Publisher server running on Heroku.
Why Fargo 2 technology is exciting. How the new CMS hooks into Fargo Publisher.
There's now a "ct" in each element in changes.json, which counts the number of times the site has been updated.
The first stats file is being maintained, changes.json.
It's a reverse-chronologic list of updated outlines.
Patterned after changes.xml which we used to bootstrap weblogs.com, in 2000.
Got boston.scripting.com:5337 up, running the latest publisher.js.
Hooked it up to Fargo -- it works.
Got redirects to work, with a module on Buffalo server.
Because Boston is running on port 5337 and not 80, I had to have this running in Frontier for now.
Going to let this config settle in for a bit, and get everyone ready for a public beta of Fargo2.
Nodejitsu didn't work out for deploying fargoPublisher. I wrote it up on the Fargo2 list.
Now we don't really have a cloning strategy for poets to run the server.
Spent the day getting node.js set up on a Linux instance on Amazon. Lots of learning. Many thanks for Dan MacTough for guiding me through it! :-)
Along the way I thought I found out why my instance stopped loading on Nodejitsu (didn't turn out to be the problem though). I changed the app from running on port 1337 to port 80. There's a Unix rule that only root can run on ports less than 1024. So I went back to 1337.
His message: "That is a permission error caused by a non privileged user trying to listen on a privileged port. Only root can listen on ports <= 1024. For now, just prefix your command with sudo. That isn't safe for production, but one step at a time. Next step will be either to listen on a nonprivileged port and use a proxy, or find a safe way to listen on port 80."
Mapped *.smallpict.com to my Nodejitsu server
Added the hostname to the string echoed on each request.
Added the wildcard to the domains element in the package.json file, although the Nodejitsu docs don't say anything about how to have a whole domain map to a NJ app.
Haven't been able to test it because NJ is calling an error on loading the new version, version 0.65.
As with a lot of this stuff, I'm floating on air, not sure what I'm doing, trying things out, and looking for something that works.
Started the worknotes file, to document work I'm actively doing on fargoPublisher.
It's an outline in the OPML folder, and a markdown file at the top level.