One of the differences between 1999.io and Fargo is that Fargo uses Dropbox for storing files while 1999.io uses the file system of the server hosting the app. The advantage I get from using Dropbox is that it provides built-in backup of my content.

The content that I write in Fargo is stored in Dropbox (source copy), published (by FargoPublisher) to Amazon S3 (second copy), which is the copy that is served by the web server portion of FargoPublisher. More copies of my content is backed up to local computers (a Mac and Windows 7 computer) using Dropbox sync. 

The current configuration that I am using for this site is storing and serving the HTML files on the same server, which is not being backed up to any other device or server. If I were to use this a production system, I will want to have a copy of the content to at least one other site.

From what I read, I think Dave is pushing the content he writes in 1999 to his S3 bucket that hosts Scripting.com, which I think is the exact approach I would like to take. (Actually, I would prefer to make FargoPublisher work in that way, but if I hitch my ride to Dave's blogging tools I have to stick with where he is focusing is attention.)