Anonymous user
Static site hosting: Difference between revisions
no edit summary
imported>Paulproteus |
imported>Paulproteus No edit summary |
||
Line 3:
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
== History ==
Line 9:
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
*
* I would prefer to use some "cloud"-esque thing like Rackspace Cloud Files or Amazon EC2+CloudFront, but none of those services let you point the root of a domain name to them.
* Both are super cheap; less than $40/yr for our needs.▼
** 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.)
* 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.
* NFS.net can manage DNS for these domains, which minimizes our hassle.
== Status ==
* Asheesh created an account with
* Right now, the "sip" shell account on linode.openhatch.org maps to the BPW website URL. Asheesh plans to set up
** In the future, maybe, the BPW repo will hopefully contain enough info (except authentication secrets) for people to do a push to
|