41–48 of 48 posts
Earlier quoted context omitted.
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/...
Earlier quoted context omitted.
Absolutely none of this is officially supported, right? (It looks very much like "game on, DotCloud", from what you've been finding, though....)
I don't think any of it's supported. Redis will run, but you can't exactly get to it (no TCP routing mesh apparently). It really just seems like they made it really easy to add new languages.
Oh, 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 ~ $
Since its fairly easy to composite multiple WSGI apps together, one could run a few different Python WSGI-based apps under a single multi-threaded process to take full advantage of the free quota. That would work with Pylons/Pyramid/Flask and other Python web frameworks that don't rely on a single set of module global settings (Django).
It looks that the new stack is based on BeeHive ( http://getbeehive.com/ ).
Earlier quoted context omitted.
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.
You can set cookies on uncached pages in ruby and read them without issue in JS on Varnish cached pages. The page will still be cached even if the user has a session cookie.
Basically: don't set or get cookies in ruby on cached pages and you'll be fine.
It looks that the new stack is based on BeeHive ( http://getbeehive.com/ ).
Um, no.
In any case, I guess you won't / can't say what you're using instead of those two? ;)