Re:Ask HN: Hosting personal site on a VPS, or in the cloud?
by jluxenberg on Sunday November 07, 2010 @12:16PM
(#1879761)
If you're running a static site, then you can host it on S3 for much cheaper than the $5 / mo you're probably paying for your VPS. All you have to do is create a CNAME www.yourdomain.com that points to bucketname.s3.amazonaws.com, then upload your site to the bucket. Make sure to set the ACLs on the objects such that they are publicly accessible, and also upload the files with the correct mime types.
For a 50MB site that transfers 5GB of data per month, you'll pay $0.61 / mo. Not too shabby, and if the site is just your resume and a few static pages you'll use much less.
Re:Ask HN: Hosting personal site on a VPS, or in the cloud?
by lacerus on Sunday November 07, 2010 @01:37PM
(#1879976)
I like this idea a lot. Can you recommend a service to take care of e-mail forwarding?
Re:Ask HN: Hosting personal site on a VPS, or in the cloud?
by AdamGibbins on Sunday November 07, 2010 @02:42PM
(#1880138)
Google Apps?
Re:Ask HN: Hosting personal site on a VPS, or in the cloud?
by jst on Sunday November 07, 2010 @03:26PM
(#1880241)
What about the root document?
Re:Ask HN: Hosting personal site on a VPS, or in the cloud?
by jluxenberg on Monday November 08, 2010 @01:04AM
(#1881571)
Very good point. I actually use NearlyFreeSpeech.net for my personal site (a pay-what-you-use host), so I'm not actually using S3, but I plan to in the future.
CloudFront apparently supports the root document, here's an article that explains how to do it: http://gothick.org.uk/2010/10/26/serving-websites-using-s3-a...
Re:Ask HN: Hosting personal site on a VPS, or in the cloud?
by thethirdswitch on Sunday November 07, 2010 @10:47AM
(#1879545)
Second this. I'm doing the same thing. Static site using StaticMatic on a VPS (Slicehost). My profile page links to Github, Twitter, posterous, etc.
I learned a lot setting up and administering my own Linux server (I have a Windows background), and use it to play around with various setups / tools.
You'd remove all the must-dos and still be able to learn a lot by administrating your own server. You can, for example, simplify deployment of your static site (fabric, capistrano, git-hooks etc), tweak performance (try different web servers, different settings and benchmark), increase security (keep up-to-date with best practices, patch software), set up ssh tunnels, a backup server, a closed version control repository and a lot more.