News for hackers. Stuff that matters.
Re:Jekyll CMS on Amazon S3 and MaxCDN by lacerus on Friday February 01, 2013 @03:41AM (#5149856)
After using Jekyll for two years with lots of hacks to have HAML and others, I switched to middleman, which has everything I need out of the box: https://github.com/middleman/middleman
Re:Jekyll CMS on Amazon S3 and MaxCDN by lukeholder on Friday February 01, 2013 @05:03AM (#5150047)
I have also. It really is wonderful.
Re:Jekyll CMS on Amazon S3 and MaxCDN by sudonim on Thursday January 31, 2013 @11:07PM (#5149143)
Current MaxCDN customer here. I'm really excited about this. I host multiple sites on Cloudfront but assets for a rails app on Maxcdn. I wanted to consolidate about a month ago. When I asked MaxCDN support why I couldn't use www, they just said no and that I should move to netdna (their other brand) to do it.

From the blog post:

"Note: MaxCDN does not automatically allow you to create a www CNAME in order to protect their system from DDoS attacks. To enable this functionality, email MaxCDN directly and mention this blog post."

I'm going to ask again and see if I can test against the experience of deploying to cloudfront. One of the things now with cloudfront is it often takes a bit of time to expire the cache.

Edit: Here's the response I received 5 mins ago from support after asking for this...

"Thanks for emailing us and I do apologize for the delayed response. I will need to escalate this to our support engineers for verification since we don't allow the use of "www" as part of custom domains for security purpose and also this needs higher level of access."

Re:Jekyll CMS on Amazon S3 and MaxCDN by jdorfman on Friday February 01, 2013 @12:41AM (#5149411)
@sudonim email me your account and I will enable it for you: jdorfman at maxcdn dot com
Re:Jekyll CMS on Amazon S3 and MaxCDN by sudonim on Friday February 01, 2013 @01:14AM (#5149504)
Awesome. Thanks for your help.
Re:Jekyll CMS on Amazon S3 and MaxCDN by byoung2 on Friday February 01, 2013 @05:52AM (#5150152)
How does a www cname open their system to ddos attacks?
Re:Jekyll CMS on Amazon S3 and MaxCDN by jdorfman on Friday February 01, 2013 @12:42PM (#5152144)
@byoung2 when we had www enabled by default, a lot of DDoS targets would sign up and point their attacks to our network effecting all of our customers. Once we disabled it, the DDoS attacks went from 1 a day to 1 every 6 months or so.
Re:Jekyll CMS on Amazon S3 and MaxCDN by byoung2 on Friday February 01, 2013 @01:34PM (#5152466)
Thanks for the clarification. So there is nothing inherent in the www cname itself, it was just that customers signing up and looking to mirror their entire site on a www cname were already being ddosed.
Re:Jekyll CMS on Amazon S3 and MaxCDN by jdorfman on Friday February 01, 2013 @04:54PM (#5153738)
exactly.
Re:Jekyll CMS on Amazon S3 and MaxCDN by pclark on Friday February 01, 2013 @12:02AM (#5149295)
Am I missing something or is Jekyll an outrageously user unfriendly blogging platform?

I have to create a text file, specify the layout, ensure the timestamp and title is in the filename, and then write HTML.

I am stunned no one has made a simple scaffold that lets me create a post with a button click and then use markdown to write, on a simple web app.

Re:Jekyll CMS on Amazon S3 and MaxCDN by jvzr on Friday February 01, 2013 @04:44AM (#5150005)
It is indeed extremely user unfriendly at the start. You have to spend a god awful amount of time setting everything up, but in the end it's worth it IMHO.

I've been blogging for 3 years now with Jekyll, and typically my "new post workflow" consists in sending an email to a private address. It's all automatic from there on.

Re:Jekyll CMS on Amazon S3 and MaxCDN by sprice on Friday February 01, 2013 @12:40AM (#5149410)
You're looking for http://prose.io, built to work with Jekyll.
Re:Jekyll CMS on Amazon S3 and MaxCDN by straws on Friday February 01, 2013 @01:10AM (#5149492)
OK, this project and that Substance editor are amazing.
Re:Jekyll CMS on Amazon S3 and MaxCDN by dbaupp on Friday February 01, 2013 @02:27AM (#5149683)
Most of your points actually mean that Jekyll is fairly simple and customisable, which is user friendly for some users. (Others don't want/need this customisability and so it is unfriendly for them.)
Re:Jekyll CMS on Amazon S3 and MaxCDN by bryogenic on Friday February 01, 2013 @12:15AM (#5149331)
Your final remark could be genuine, but I would rather assume you are sarcastically talking about github pages [http://pages.github.com/].
Re:Jekyll CMS on Amazon S3 and MaxCDN by jvc26 on Friday February 01, 2013 @03:05AM (#5149775)
Um, you can use Markdown, and in the context of Github pages (http://pages.github.com/), that is exactly what you're talking about ...
Re:Jekyll CMS on Amazon S3 and MaxCDN by hayksaakian on Friday February 01, 2013 @04:09AM (#5149925)
I was genuinely unaware of the connection here. Thanks for posting that.
Re:Jekyll CMS on Amazon S3 and MaxCDN by kevinSuttle on Friday February 01, 2013 @11:55AM (#5151845)
1. Jekyll isn't a CMS per se. (I know this is a nitpicky thing) 2. GH-Pages actually performs a ton of server-side optimizations.

I use it, and my site currently scores 95 on YSlow. You can't use .htaccess on GH-Pages, yet, this is what they do for you: http://d.pr/i/81zP Note that the grade E in that is my fault. I have a favicon URI, but I never uploaded a favicon. Everything else is optimized automatically.

Re:Jekyll CMS on Amazon S3 and MaxCDN by hayksaakian on Thursday January 31, 2013 @10:09PM (#5148967)
How does Jekyll + S3 + CDN compare to dynamic rails site with russian doll caching (cache digests) using something like redis?
Re:Jekyll CMS on Amazon S3 and MaxCDN by benmanns on Thursday January 31, 2013 @10:34PM (#5149056)
You'll likely get similar performance as long as your comparison is between Jekyll + S3 + CDN and Rails + Caching + CDN. Otherwise, the worldwide caching in CDNs will outperform the Rails app in a single region.
Re:Jekyll CMS on Amazon S3 and MaxCDN by HeyImAlex on Friday February 01, 2013 @02:52AM (#5149741)
Similar/better performance, dirt cheap prices, practically infinite scalability and (potentially vastly) increased simplicity.
Re:Jekyll CMS on Amazon S3 and MaxCDN by danneu on Friday February 01, 2013 @12:35AM (#5149397)
Jekyll == (Rails + page caching)
Re:Jekyll CMS on Amazon S3 and MaxCDN by kerno on Friday February 01, 2013 @12:40AM (#5149409)
We're very interesting is maximising site speed (which we are currently reviewing - too many plugins slowing things our Wordpress site up) but I don't think we could easily manage to produce a new post everyday using a static site generator - am I wrong?
Re:Jekyll CMS on Amazon S3 and MaxCDN by dbaupp on Friday February 01, 2013 @02:28AM (#5149687)
What problems do you see that would stop you from posting everyday?
Re:Jekyll CMS on Amazon S3 and MaxCDN by eli on Thursday January 31, 2013 @10:59PM (#5149128)
Any particular reason to use MaxCDN over CloudFront?

Edit: just realized why that's a silly question. Would still be curious to hear the answer though.

Re:Jekyll CMS on Amazon S3 and MaxCDN by ccorda on Thursday January 31, 2013 @11:39PM (#5149238)
I made this decision just this week, biggest reason being gzip compression. S3 will only store your file compressed or uncompressed, and you have to do server-side gzip detection to request the proper version, which isn't possible with CloudFront. [1]. You also have to gzip compress locally and upload both versions.

With MaxCDN, I just upload uncompressed, and it will gzip upon request certain text file types (xml, js, css, etc.) [2].

[1] http://blog.kenweiner.com/2009/08/serving-gzipped-javascript...

[2] http://www.cdnplanet.com/compare/cloudfront/netdna/

Re:Jekyll CMS on Amazon S3 and MaxCDN by HeyImAlex on Friday February 01, 2013 @02:06AM (#5149633)
I feel like this is almost a non issue unless you're running a site that absolutely needs to run everywhere since the last browsers that shipped without gzip support were released in what, 1998? A significant portion of your users (according to O'Reilly's 2009 _Even Faster Websites_, around 15%) don't say they can support gzip even though they can. Just ignoring Accept-Encoding headers and serving only gzipped content is probably good enough for 99% of people and likely gives you slightly better overall performance on average than actually respecting whatever the request headers say.
Re:Jekyll CMS on Amazon S3 and MaxCDN by jdorfman on Friday February 01, 2013 @03:01AM (#5149760)
@HeyImAlex A week ago I would have totally agreed with you. I asked a friend and he told me "replace the user-agent with a misconfigured upstream proxy and you run the risk of serving an uncompressed version to end user that supports gzip, and vice versa."
Re:Jekyll CMS on Amazon S3 and MaxCDN by eli on Wednesday February 06, 2013 @11:53AM (#5177427)
Sounds dangerous, but if you try it out on a popular site, I'd love to hear your results!
Re:Jekyll CMS on Amazon S3 and MaxCDN by tantalor on Friday February 01, 2013 @02:11AM (#5149644)

  On the Obama campaign we made our donate pages 60%
  faster and got a 14% increase in donation conversions.
Did they test this? For what purpose? We've known this is true since 2006.

http://www.zdnet.com/blog/btl/googles-marissa-mayer-speed-wi...

Re:Jekyll CMS on Amazon S3 and MaxCDN by the1 on Thursday January 31, 2013 @11:10PM (#5149151)
or just start blogging on gist.github.com. your blog url is http://gist.github.com/<your-github-id>;
Re:Jekyll CMS on Amazon S3 and MaxCDN by molecule on Thursday January 31, 2013 @11:44PM (#5149249)
Boto is awesome for interacting w/ AWS, but managing an application stack in ruby (jekyll) and a deployment stack in python (https://gist.github.com/4596766) does not seem optimal.