Heroku Announces New Version: “Celadon Cedar”
news.heroku.com
Heroku Announces New Version: “Celadon Cedar”
1–10 of 48 posts
Re: Heroku Announces New Version: “Celadon Cedar”
#2it 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!
Re: Heroku Announces New Version: “Celadon Cedar”
#3it 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!
Take a look at the documentation below:
Re: Heroku Announces New Version: “Celadon Cedar”
#4it 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!
Take a look at the documentation below: http://devcenter.heroku.com/articles/cedar http://devcenter.heroku.com/articles/node-js
great, thanks for the links!
Re: Heroku Announces New Version: “Celadon Cedar”
#5Oh, hey, it appears you can run python stuff too:
https://gist.github.com/0a08e676559fc03e6200
kurt$ heroku run bash
Running bash attached to terminal... up, run.2
~ $ python -V
Python 2.7.1
~ $Re: Heroku Announces New Version: “Celadon Cedar”
#6Oh, hey, it appears you can run python stuff too: https://gist.github.com/0a08e676559fc03e6200 kurt$ heroku run bash Running bash attached to terminal... up, run.2 ~ $ python -V Python 2.7.1 ~ $
Huh, so the Python support is pretty complete:
Simple Flask app: https://gist.github.com/efec5e060e88abc87821
Python/Django: https://gist.github.com/866c79035a2d066a5850
Re: Heroku Announces New Version: “Celadon Cedar”
#7Fantastic! 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?
Re: Heroku Announces New Version: “Celadon Cedar”
#8Oh, hey, it appears you can run python stuff too: https://gist.github.com/0a08e676559fc03e6200 kurt$ heroku run bash Running bash attached to terminal... up, run.2 ~ $ python -V Python 2.7.1 ~ $
Huh, so the Python support is pretty complete: Simple Flask app: https://gist.github.com/efec5e060e88abc87821 Python/Django: https://gist.github.com/866c79035a2d066a5850
Wow, it gets even more interesting:
/tmp $ cd redis-2.2.8/
/tmp/redis-2.2.8 $ make
/tmp/redis-2.2.8 $ cd src
/tmp/redis-2.2.8/src $ ./redis-server
[295] 31 May 15:36:30 # Warning: no config file specified, using the default config. In order to specify a config file use 'redis-server /path/to/redis.conf'
[295] 31 May 15:36:30 * Server started, Redis version 2.2.8
[295] 31 May 15:36:30 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
[295] 31 May 15:36:30 * The server is now ready to accept connections on port 6379
[295] 31 May 15:36:30 - 0 clients connected (0 slaves), 790480 bytes in use
[295] 31 May 15:36:35 - 0 clients connected (0 slaves), 790480 bytes in use
[295] 31 May 15:36:40 - 0 clients connected (0 slaves), 790480 bytes in useRe: Heroku Announces New Version: “Celadon Cedar”
#9The use of LXC containers now is quite interesting for security.
"- Full isolation of processes for security and performance"
Have there been security-related incidents before with their slugs? Is this to address safer multi-tenancy?
Re: Heroku Announces New Version: “Celadon Cedar”
#10I just created my first Node.js app. Clone ry's demo at:
https://github.com/ry/node_chat
Add a Procfile and package.json per the docs:
http://devcenter.heroku.com/articles/node-js
And it just works: