Live data from Hacker News

Heroku Announces New Version: “Celadon Cedar”

news.heroku.com

31–40 of 48 posts

Re: Heroku Announces New Version: “Celadon Cedar”

#31
post #30
post #28

Earlier quoted context omitted.

I expect that someone will build a Varnish add on for Heroku. It even looks possible to run Varnish on a dyno, believe it or not. I love Varnish, but it's completely inflexible in Heroku so it's always been a mixed blessing. Sticking Google Analytics on your page, for instance, creates cookies for users that mean they will no longer get cached content. It's something that I can work around with dedicated Varnish, but…

That's not true. Google Analytics cookies are injected via JS. When heroku's Varnish is checking for a cached version of the page, it strips any cookie information given by the browser. We've are running production apps with Varnish caching + Google Analytics without issue. Set your cookies with JS or on uncached pages (such as POST logins) and you'll be fine.

It's possible that it strips the GA cookies (which is cool, I had no idea), but Varnish doesn't strip cookie information from the browser. If it did you wouldn't get any Rails sessions or anything.

Re: Heroku Announces New Version: “Celadon Cedar”

#32
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. http://devcenter.heroku.com/articles/billing-changes

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?

Re: Heroku Announces New Version: “Celadon Cedar”

#33

I 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: http://node-chat.herokuapp.com/

It worked for me too :) but check up your billing usage statement it will be showing some charges, even though you are under free limit. I just filed a support ticket with heroku, after scaling the web dyno to 0 ;)

Re: Heroku Announces New Version: “Celadon Cedar”

#35

The 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?

Have there been security-related incidents before with their slugs?

Absolutely. http://daverecycles.com/post/2858880862/heroku-hacked-dissec...

Re: Heroku Announces New Version: “Celadon Cedar”

#36
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.)

Re: Heroku Announces New Version: “Celadon Cedar”

#39

Earlier quoted context omitted.

Very interested to hear this as well. Anyone from Heroku can comment?

LXC is one of several isolation layers used in the Heroku dyno manifold to ensure process security and resource guarantees. Here is a more in-depth discussion of Heroku dyno isolation: http://devcenter.heroku.com/articles/dyno-isolation .

So LXC is fully secure now if you stick to chroot?

http://www.mail-archive.com/lxc-users@lists.sourceforge.net/...

Re: Heroku Announces New Version: “Celadon Cedar”

#40
post #32

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. http://devcenter.heroku.com/articles/billing-changes This means any proce…

No, that's the long and short of it.

Of course, you can't share multiple apps behind one domain, so if the one dyno isn't keeping you you'll need to scale up and pay for it.

OTOH, if you don't need to worry about any extra latency (maybe?) you could probably get away with a rails+node app like https://github.com/maccman/holla running free by having one app just run the web interface, and point the backend at another app running node.

As soon as you go outside of one tech stack it's cheaper to just get a small VPS to start with, but heroku definitely has its perks.

Post reply on HN