Heroku's cedar stack can now detect apps using: * Ruby * Node.js * Clojure * Python * Go ?? * Scala * PHP * Java * Perl ?? Anything missing here? That covers a lot of whats out there.
Everything else? Because you can just deploy anything actually?
Python and Django on Heroku
61–70 of 75 posts
Re: Python and Django on Heroku
#62Anyone know if there's a self-contained way to spool up a dyno sporadically to complete scheduled tasks? I have a webapp now that's hosted on a VPS and uses Celery to schedule tasks. The tasks themselves only take about a second, the dyno needs to stay active for ~5 minutes to service a bunch of HTTP requests from another webservice that will result from the task, and then shut down until the next task. There are O(1…
Use a single dyno, and set the caller's HTTP timeout threshold to a high enough point that it can deal with the delay associated with reallocating your app.
Re: Python and Django on Heroku
#63Earlier quoted context omitted.
> ...but what sets them apart now? As a very happy user of some of Python PaaS services [1], there are a few reasons why I don't see myself switching to Heroku: * These services are written by our community, for our community. The principles at most of these companies are people I've known for years. I've reviewed their code; they've reviewed mine. We'd argued, commiserated, and bought each other whiskey. They've hel…
> These services are written by our community, for our community. The principles at most of these companies are people I've known for years. Of all the points you raise, this is probably the least relevant in business terms. PaaS is about opening up platforms to all comers; one's standing in relatively insular language communities doesn't say much about one's marketability outside those communities.
> Of all the points you raise, this is probably the least relevant in business terms.
He wasn't listing business reasons per se - He was listing reasons why he isn't considering Heroku. And that's a very valid reason - work with people you know and trust, rather than be a second class citizen at a primary ruby PaaS.
Re: Python and Django on Heroku
#64Earlier quoted context omitted.
> These services are written by our community, for our community. The principles at most of these companies are people I've known for years. Of all the points you raise, this is probably the least relevant in business terms. PaaS is about opening up platforms to all comers; one's standing in relatively insular language communities doesn't say much about one's marketability outside those communities.
> Of all the points you raise, this is probably the least relevant in business terms. He wasn't listing business reasons per se - He was listing reasons why he isn't considering Heroku. And that's a very valid reason - work with people you know and trust, rather than be a second class citizen at a primary ruby PaaS.
heroku used to be a ruby paas. calling it a ruby paas or primary ruby paas is not fair as now it supports node.js, clojure, java and python along with ruby.
Re: Python and Django on Heroku
#65Python 2.7? They’re years ahead of Google App Engine! Addendum: The previous statement is slightly tongue-in-cheek, but: (1) GAE is running a version of Python (2.5) so old, that it’s hard to get fully patched binaries of it anymore (depending on your platform); and (2) By “years ahead,” I don’t mean it will take Google years to catch up, but merely that their Python version is years old. Puzzling, given that Guido w…
App Engine announced they will release a Python 2.7 runtime in several months. It's currently in their trusted tester program.
I can confirm this. It's also very easy to switch old apps to 2.7.
Re: Python and Django on Heroku
#66Earlier quoted context omitted.
> Of all the points you raise, this is probably the least relevant in business terms. He wasn't listing business reasons per se - He was listing reasons why he isn't considering Heroku. And that's a very valid reason - work with people you know and trust, rather than be a second class citizen at a primary ruby PaaS.
heroku used to be a ruby paas. calling it a ruby paas or primary ruby paas is not fair as now it supports node.js, clojure, java and python along with ruby.
There is a significant difference between "supports" and "optimized and designed for". I think Heroku is awesome, but I'm still going to give them at least another 9-12 month or so to sort out all the kinks before I'd trust them as a python PaaS.
Re: Python and Django on Heroku
#67Earlier quoted context omitted.
> Of all the points you raise, this is probably the least relevant in business terms. He wasn't listing business reasons per se - He was listing reasons why he isn't considering Heroku. And that's a very valid reason - work with people you know and trust, rather than be a second class citizen at a primary ruby PaaS.
heroku used to be a ruby paas. calling it a ruby paas or primary ruby paas is not fair as now it supports node.js, clojure, java and python along with ruby.
For some value of "supports" that apparently doesn't leave Jacob comfortable that it gets equal developer attention at Heroku. Of course the other language support could be perfect ... I'll prefer to trust the opinions of people I know with no apparent axe to grind.
Re: Python and Django on Heroku
#68I loved Heroku, many moons ago when I was working in Rails. As I've emigrated away from Rails to Django, I've found dotcloud to be the premiere platform -- I want to qualify this, it is the premiere polyglot platform, but for each individual environment I've deployed on dotcloud, their experience has been the best. I haven't used dotcloud's Ruby/Rails stack, so I can't compare that, but Heroku is definitely fighting…
Any reason why you left Rails for Django?
Re: Python and Django on Heroku
#69Does anyone know if the stack will only support WSGI or could I also run a Tornado instance on the cedar stack? I know when I tried dotcloud several months ago it only supported WSGI.
Re: Python and Django on Heroku
#70I loved Heroku, many moons ago when I was working in Rails. As I've emigrated away from Rails to Django, I've found dotcloud to be the premiere platform -- I want to qualify this, it is the premiere polyglot platform, but for each individual environment I've deployed on dotcloud, their experience has been the best. I haven't used dotcloud's Ruby/Rails stack, so I can't compare that, but Heroku is definitely fighting…
Any reason why you left Rails for Django?
Broadening my horizons? I'm not a Ruby genius, and I really like the Python/Django mindset of "not being clever". The code is MUCH more readable, especially to laypersons, and I value very highly the capability of revisiting my code a year later and knowing exactly what I was doing with it.
I never really felt that way with Ruby, though I still like and occasionally use it. I'm actually working on a Ruby project right now, mostly due to circumstance (hosting was donated for the project, and it supports RoR but not Django or Flask).
The other main thing, at the time, was that there were a LOT of very valid options with Python. I could crank out small projects very quickly in Flask or Tornado, work on larger, more custom solutions with Django, or if it was pretty cookie-cutter, fall back to Zope. At the time, AppEngine and web2py were catching on as well. For the most part, a module written for one of those ports really easily to any of the others.
Bottom line though, learning one has really made me a better programmer and taught me to appreciate the WHY behind some of the decisions a given framework has made. If you only know one, I encourage you to look at the other side of things, even if just for perspective.