Support Managing HTML Configuration Files

[antgiant]

As has been mentioned in both #27 and #35 it would be very nice to be able to manage the HTML WatchApp configuration files within CloudPebble. Since @Katharine requested in #27 that a destination be decided on before implementing the editor I would like to use this issue to decide on a preferred destination.

As I see it the primary options are

1. Config files are integrated (I.E. Integrate Pebble Autoconfig #35 Autoconfig)
2. Pebble hosts the HTML files
3. Github hosts the HTML files (I.E. gh-pages branch)
4. Dropbox or some other cloud service hosts the HTML files

What do you vote for?

[antgiant]

I vote for 1 as I really like having the WatchApp fully manageable even when the phone is offline.

2 is my second choice as much of Pebble already relies on the Pebble web infrastructure. However I strongly doubt that Pebble is willing to do that or I suspect that it would already be done.

3 is my third choice as I think it could be a relatively simple extension of the existing Git support. Simply create a configuration subfolder that pushes to the gh-pages branch of the selected project instead of the selected branch, and add a configuration toggle to turn it on. Something similar to this concept https://gist.github.com/chrisjacob/833223