They all work well and scale since they're static. I did one method that wasn't static, using XML-RPC. That method had problems as the installed base of Frontier grew. Static distribution is the way to go. #
As I waited for a response to the query about folder-level sync with a git repository, I went ahead with the brute force method, which works as follows.#
When it's time to sync, first we clone the whole repo into a temp folder. Then compare the destination folder with the sub-folder of the downloaded repo, copy the new or changed files. Then delete the temporary repo.#
The assumption is that the repo is relatively small. We burn a bit of bandwidth and temporary disk space. And the job gets done. #
The overall system I'm working on will also support one-way sync with an S3 location and perhaps RSS-based delivery later. But right now having git-based distribution working, I can proceed. #
Last update: Saturday October 19, 2019; 10:27 AM EDT.
You know those obnoxious sites that pop up dialogs when they think you're about to leave, asking you to subscribe to their email newsletter? Well that won't do for Scripting News readers who are a discerning lot, very loyal, but that wouldn't last long if I did rude stuff like that. So here I am at the bottom of the page quietly encouraging you to sign up for the nightly email. It's got everything from the previous day on Scripting, plus the contents of the linkblog and who knows what else we'll get in there. People really love it. I wish I had done it sooner. And every email has an unsub link so if you want to get out, you can, easily -- no questions asked, and no follow-ups. Go ahead and do it, you won't be sorry! :-)