I'm learning to code by building 180 websites in 180 days. Today is day 115

Re:I'm learning to code by building 180 websites in 180 days... by robbles on Wednesday July 24, 2013 @02:16PM (#6097993)

If you're just building static website (HTML/CSS/JavaScript), I highly recommend just using S3:

http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosti...

Quick guide:

- Create a bucket for each website, named after the domain (e.g. "myproject.mysite.com")

- Turn on static website hosting for the bucket (through the AWS Console)

- Go to your DNS provider and create a "CNAME" record pointing "myproject.mysite.com" to "myproject.mysite.com.s3-website-us-west-1.amazonaws.com" (The AWS Console will give you the exact domain to use here)

- For super-easy deployment, use s3cmd's sync utility (http://s3tools.org/s3cmd-sync) to upload all changed files in your project:

    $ s3cmd -v sync ./ s3://myproject.mysite.com/ --acl-public

[ Parent | on HN ]

Re:I'm learning to code by building 180 websites in 180 days... by bananamansion on Wednesday July 24, 2013 @11:24PM (#6100734)

s3? ... but couldn''t you just host a static site on github for free? whats the difference between the two?

[ Parent | on HN ]

Re:I'm learning to code by building 180 websites in 180 days... by IanChiles on Thursday July 25, 2013 @11:07AM (#6102800)

S3 isn't free, but is slightly easier to start with IMO. Besides that, no difference.

[ Parent | on HN ]

Re:I'm learning to code by building 180 websites in 180 days... by robbles on Tuesday July 30, 2013 @12:59AM (#6125440)

You can, but then you need to stay within the limitations of GitHub pages:

- Needs to be versioned with git to be deployed

- Space limitation (I assume, not sure what it is)

- Deploying new content to S3 is a lot faster - github pages has some sort of build process with a substantial delay

[ Parent | on HN ]