Heroku Announces New Version: “Celadon Cedar”

Oh, hey, it appears you can run python stuff too: <a href="https://gist.github.com/0a08e676559fc03e6200" rel="nofollow">https://gist.github.com/0a08e676559fc03e6200</a><p><pre><code> kurt$ heroku run bash Running bash attached to terminal... up, run.2 ~ $ python -V Python 2.7.1 ~ $</code></pre>

I just created my first Node.js app. Clone ry's demo at:<p><a href="https://github.com/ry/node_chat" rel="nofollow">https://github.com/ry/node_chat</a><p>Add a Procfile and package.json per the docs:<p><a href="http://devcenter.heroku.com/articles/node-js" rel="nofollow">http://devcenter.heroku.com/articles/node-js</a><p>And it just works:<p><a href="http://node-chat.herokuapp.com/" rel="nofollow">http://node-chat.herokuapp.com/</a>

<i>Cedar now allows you to scale any dyno as low or high as needed, including all the way down to 0. This means you could choose to scale your web dyno down to 0 and a worker to 1. If left this way for the entire month you would have 720 worker dyno-hours and 0 web dyno-hours total at the end of the month, fully inside the 750 available per month.</i> <a href="http://devcenter.heroku.com/articles/billing-changes" rel="nofollow">http://devcenter.heroku.com/articles/billing-changes</a><p>This means any process type, for example cron jobs, for free. As long as only one process is ran per app, but as far as I know, you can run as many apps as you want. This sounds like a very nice deal. Am I missing something?

It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc.<p>Will the old configuration style for http caching continue to be supported indefinitely?

"LXC used as a container for all dynos running on Celadon Cedar"<p>Has anybody published a complete SELinux or SMACK policy to use LXC with untrusted users? Last I checked LXC wasn't fully ready yet.

The use of LXC containers now is quite interesting for security.<p>"- Full isolation of processes for security and performance"<p>Have there been security-related incidents before with their slugs? Is this to address safer multi-tenancy?

Blog post with code examples is here - much better than press release: <a href="http://blog.heroku.com/archives/2011/5/31/celadon_cedar/" rel="nofollow">http://blog.heroku.com/archives/2011/5/31/celadon_cedar/</a>

This is beautiful. I like how they got rid of Varnish. The problem with Varnish was that you couldn't test it in your local development environment. (Heroku wouldn't give out their Varnish configuration, so you could only make an educated guess as to how their Varnish was configured.)

Fantastic! I am glad to see support for HTTP 1.1. Anyone know if unicorn/Rails 3.1 chunked responses will work out of the box?

It looks that the new stack is based on BeeHive (<a href="http://getbeehive.com/" rel="nofollow">http://getbeehive.com/</a>).

This is exciting stuff. I have been learning Ruby on Rails and will be pushing my code to Heroku soon.

Full native Node.js support. Alright!

Anyone find that grey on grey text a little hard to read?

it would makes sense if the documentation and the API had been updated before they did the press release. otherwise, great news for node.js people!