Host images outside main repo

[jeromew21]

The repo hosts a lot of images, so cloning/pushing takes way too long. It's also best practice AFAIK to host images on a CDN. I'm not sure the of logistics concerning this project, but it could be worthwhile in the long run.

[quantumfusion]

Love the initiative. Fogey here to chime in with institutional and industry knowledge. And bonus points for a fun problem that I happen to see as I was checking in on something Kevin asked me to look into.

Lets also think about how we will track those assets. Sure, you can have all of the images managed on a CDN, however, how will you maintain the src urls that are in the jekyll templates in this repo?

Also, since I saw some references to Travis and such in some earlier commits to master, there are multiple times where the templates are being interpreted, which allows for some levels of double-checking to make sure that files actually exist.

[jeromew21]

I'll look in to the Travis CI for Jekyll.

For the actual hosting itself, what do you suggest? What CDN would be best to host our images? I know S3 has a nice API, but don't really know of any alternatives.

[quantumfusion]

Some extra things to think about when setting this up:

1. The website serves both pioneers.berkeley.edu and pierobotics.org. Images should be fine, but you may need to look into some CORS related stuff for any JS.
2. Dokku supports deployment hooks, so it may be possible to have some scripts run when a new version is pushed to apple that will push the static content up to the CDN of choice: http://dokku.viewdocs.io/dokku/advanced-usage/deployment-tasks/