Using GitHub to share Frontier code

When Brent Simmons was talking about storing object databases in the file system on the Frontier-user list, I had a nagging feeling I had done something in this area. I had. Not even that long ago.

Here's the story.

I have a tool called gitHub.root that periodically checks the contents of a set of odb's you specify and exports any changed scripts to a folder structure, designed to by shared on GitHub.

I'm not releasing that tool at this time, because I want to do another review. But I am USING it, to release the code for another tool, this one is current, and you can download it from the Tools Catalog page in the OPML Editor website (choose Tools Catalog from the Misc menu). It works. I'm using it all the time. It's called superSync. It really is super and it does a nice job of syncing local folders to locations on Amazon S3. I have some software in the pipe that needs this functionality.

Anyway, it's both a Tool and a GitHub repo.

https://github.com/scripting/superSync/tree/master

The docs are right there, in the Readme.md file.

I'm not taking pull requests, this is just for sharing, and you're welcome to fork it and do with it as you please. MIT License.


Last built: Thu, Apr 17, 2014 at 10:38 PM

By Dave Winer, Saturday, December 14, 2013 at 11:25 AM. Pay no attention to the man behind the curtain.