Hold on a sec here. I thought of another approach last night that could work and we don't have to manage a web server. Here are the steps that the CloudBees build would take.
1. Site gets built by jekyll. 1. Site gets uploaded to Cloud Files container with a little bit of jclouds code. 1. Container gets CDN enabled on it so it can operate as a "[Static Website](http://docs.rackspace.com/files/api/v1/cf-devguide/content/Create_Static_Website-dle4000.html)". 1. URL to the static website is spit out in the CloudBees build (e.g. http://595ae8a4488249074e76-63df099925463e6a35e71531aa339bb1.r81.cf2.rackcdn.com) Each build produces a unique container and URL. Because it has it's own subdomain we shouldn't need to fiddle around making everything relative. I.E. We shouldn't even need the changes in this PR. Contributor and committer can review the site without worrying about it getting overwritten because it's unique. Containers will be removed periodically by a script that cleans out our Rackspace test account. Thoughts on this approach before I head down this path? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/2#issuecomment-20887642
