Deploy Websites on Amazon S3 using Jekyll and Git

#1

Post by soren » Sun, Feb 20, 2011, 1:23 PM UTC

Deploy Websites on Amazon S3 using Jekyll and Git
openfoo.org

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#2

Post by luigi » Sun, Feb 20, 2011, 1:52 PM UTC

This is a very useful writeup.

But using S3 for static sites comes with a big caveat: You can't host root domains on it because you need to use a CNAME to point to S3. And a CNAME must be a subdomain; it can't be a root domain.

I set up a petition to Amazon to point out the problem:

http://act.ly/34u

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#3

Post by kersny » Sun, Feb 20, 2011, 1:57 PM UTC

I just set up something very similar last night, without git. I used http://s3tools.org/s3cmd in a simple bash script, which nicely replaced my previous rsync setup. Should be about $0.01 a month to run :)

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#4

Post by danohuiginn » Sun, Feb 20, 2011, 2:01 PM UTC

Dr. Jekyll and Mr. Git? I guess at least it brings out the contrast more clearly than Stevenson's original title

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#5

Post by AdamGibbins » Sun, Feb 20, 2011, 2:07 PM UTC

luigi wrote: post #2

This is a very useful writeup. But using S3 for static sites comes with a big caveat: You can't host root domains on it because you need to use a CNAME to point to S3. And a CNAME must be a subdomain; it can't be a root domain. I set up a petition to Amazon to point out the problem: http://act.ly/34u

Put WWW. on it and as a temp fix use someone like Nearly Free Speech to host the root domain with nothing but a redirect on.

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#6

Post by luigi » Sun, Feb 20, 2011, 2:17 PM UTC

AdamGibbins wrote: post #5

luigi wrote: post #2

This is a very useful writeup. But using S3 for static sites comes with a big caveat: You can't host root domains on it because you need to use a CNAME to point to S3. And a CNAME must be a subdomain; it can't be a root domain. I set up a petition to Amazon to point out the problem: http://act.ly/34u

Put WWW. on it and as a temp fix use someone like Nearly Free Speech to host the root domain with nothing but a redirect on.

I don't want a www. on it.

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#7

Post by AdamGibbins » Sun, Feb 20, 2011, 2:33 PM UTC

luigi wrote: post #6

AdamGibbins wrote: post #5

Earlier quoted context omitted.

Put WWW. on it and as a temp fix use someone like Nearly Free Speech to host the root domain with nothing but a redirect on.

I don't want a www. on it.

OK, don't then. I was just suggesting a temporary fix as its unlikely Amazon will fix this any time soon.

Also be aware that their are benefits to hosting your site on www. - its not just for historical reasons. e.g. the ability to restrict cookies to the subdomain - which you can't do with root domains as it affects all subdomains also.

Not to mention people will some people will still go to www. by default anyhow so you're always going to have to have a www.

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#8

Post by moe » Sun, Feb 20, 2011, 3:37 PM UTC

AdamGibbins wrote: post #7

luigi wrote: post #6

Earlier quoted context omitted.

I don't want a www. on it.

OK, don't then. I was just suggesting a temporary fix as its unlikely Amazon will fix this any time soon. Also be aware that their are benefits to hosting your site on www. - its not just for historical reasons. e.g. the ability to restrict cookies to the subdomain - which you can't do with root domains as it affects all subdomains also. Not to mention people will some people will still go to www. by default anyhow s…

which you can't do with root domains as it affects all subdomains also.

rfc2109 disagrees:

  A is a FQDN string and has the form NB, where N is a non-empty name
  string, B has the form .B', and B' is a FQDN string.  (So, x.y.com
  domain-matches .y.com but not y.com.)

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#9

Post by hayley » Sun, Feb 20, 2011, 3:39 PM UTC

luigi wrote: post #2

This is a very useful writeup. But using S3 for static sites comes with a big caveat: You can't host root domains on it because you need to use a CNAME to point to S3. And a CNAME must be a subdomain; it can't be a root domain. I set up a petition to Amazon to point out the problem: http://act.ly/34u

I setup a so-called naked domain and pointed it at an Amazon S3 CNAME just fine.

I believe the big downside is that I'll never be able to use email on that domain because of the CNAME. Which, for me, wasn't a big deal.

Re: Deploy Websites on Amazon S3 using Jekyll and Git

#10

Post by zepolen » Sun, Feb 20, 2011, 4:15 PM UTC

moe wrote: post #8

AdamGibbins wrote: post #7

Earlier quoted context omitted.

OK, don't then. I was just suggesting a temporary fix as its unlikely Amazon will fix this any time soon. Also be aware that their are benefits to hosting your site on www. - its not just for historical reasons. e.g. the ability to restrict cookies to the subdomain - which you can't do with root domains as it affects all subdomains also. Not to mention people will some people will still go to www. by default anyhow s…

which you can't do with root domains as it affects all subdomains also. rfc2109 disagrees: A is a FQDN string and has the form NB, where N is a non-empty name string, B has the form .B', and B' is a FQDN string. (So, x.y.com domain-matches .y.com but not y.com.)

That's his point, setting a cookie on the root "domain.com" will mean it's sent to "www.domain.com" or "blog.domain.com" as well. You mostly do not want this.