Static site hosting

From OpenHatch wiki
Revision as of 19:14, 19 November 2011 by imported>Paulproteus (→‎Rationale for Rackspace Cloud Files)

Summary

Many of the sites created by OpenHatch are purely static files. This includes the Campus Outreach site at http://campus.openhatch.org/ and the Boston Python Workshop website at http://bostonpythonworkshop.com/.

So far, we have hosted these sites on the main OpenHatch linode. We're in the process of moving them to Rackspace Cloud Files.

History

On November 19, 2011, the main OpenHatch linode had an outage. This meant that all the sites hosted on it, including these static sites, were down. Jessica McKellar urged us to find a more reliable, well-monitored hosting situation for the Boston Python Workshop.

Rationale for Rackspace Cloud Files

  • Normally I would go with NearlyFreeSpeech.NET. They have about 2 hours of downtime every 4 years, and they schedule these outages in advance. I feel more comfortable putting our files on a hosting service where we believe the hosting company is big enough to geographically spread its data around multiple data centers. (Perhaps NFS does this as well; I'm not sure.)
  • Both are super cheap; less than $40/yr for our needs.
  • Rackspace Cloud Files has an SLA that guarantees 99.9% uptime, but I would say the SLA has no "teeth" -- they will simply refund portions of your month's hosting costs, which to us is very little money. You can read it here: http://www.rackspace.com/cloud/cloud_hosting_products/files/faq/
  • In general, I strongly prefer to put static sites with hosts that understand how easy it is to serve static sites. NearlyFreeSpeech.NET and Rackspace Cloud Files and others have clear provisions for marking sites as static, which indicates they have a clue.

Status

  • Asheesh created an account with Rackspace Cloud Files. Username = openhatch; password is randomly generated.
  • Right now, the "sip" shell account on linode.openhatch.org maps to the BPW website URL. Asheesh plans to set up the "sip" shell account to have the info + authentication secrets to push the files to Rackspace Cloud Files rather than have Apache/nginx serve them out of /home/sip/.
    • In the future, maybe, the BPW repo will hopefully contain enough info (except authentication secrets) for people to do a push to Rackspace Cloud Files