"Deploy GAE sites with ease by pushing them to GitHub with our software solution." (14 words)
So how does DryDrop work? It's simple - if you have a GitHub repository that includes a static website you want to host on App Engine, DryDrop can be easily uploaded as your App Engine project. Once you upload it for the first time, simply set up the post-receive hook in your GitHub repo to point to your App Engine project. This way every change you push to GitHub will be reflected on your App Engine site immediately.
When a visitor comes to your App Engine site, DryDrop has a simple cache in place. If the requested page is not already stored in the cache, DryDrop will fetch it from GitHub, store it in the cache, and then serve it. The next time the same URL is requested, it will be served directly from DryDrop's cache.
Suppose you make changes to your files. In the instant that you push those file changes into GitHub, the post-receive hook will ping DryDrop, invalidating the modified files in the cache. The next request for the same content will trigger the downloading of fresh files from GitHub.
Overall, DryDrop is a must-have for anyone looking to simplify the process of hosting a static website on Google App Engine and updating it via GitHub. With its easy setup and functionality, it's definitely worth giving a try.
Version 0.2: N/A