Django on Heroku running with Celery
21–30 of 47 posts
Re: Django on Heroku running with Celery
#22Re: Django on Heroku running with Celery
#23Are there any drawbacks to this? I've been looking for a "Heroku for Django" for a few months and I just started using Google App Engine to get some of what I want. I'll go ahead and try this if it works well.
It's also worth mentioning that unlike AppEngine the Heroku stack is a unix based environment (call "heroku run bash" and boom, you have shell access) and its components are all open sourced, so it should be relatively easy to move from there to a VPS if you ever need to.
Other than that, Heroku comes from multiple years of supporting Ruby (and some Node.js), their main page still states "Agile deployment for Ruby and Node.js", there's a lot of Rails/Sinatra/Rack specific stuff in their docs, and the Heroku command line tool is a Ruby Gem. In other words, this is not an "Heroku for Django", like Djangy was, it's become more like an "Heroku for anything, with a strong culture of Ruby", and IMO that's extremely exciting: we're talking about access to multiple languages and tools on the same easy-to-use cloud.
Re: Django on Heroku running with Celery
#24Looks like the market for "push-hosting" django (suddenly?) increased much more than that existed for ruby frameworks.
AFAI am concerned, WebFaction, Linode, Slicehost, EC2 more than addressed what I wanted for a while.
Not that I don't like these or that they don't make my life simpler- They very much do. But is there room for so many? Do I just forget the Apache VirtualHost config details, as I may never need that again?
Re: Django on Heroku running with Celery
#25Earlier quoted context omitted.
I disagree: your statement does not in fact reflect conventions on common readability. If anything, a programmer should be able to read s = s + (...) just as well as s += (...). They both seem obvious to me but as a Python programmer, I prefer the latter.
Read it again, says "could be argued," not that I am in unrelenting agreement with it. I find both obvious as well. However, one of python's main design goals is readability. That's why it does not have the i++ operator in preference to i = i + 1, for example. No switch keyword either. +=, etc managed to squeeze in though. More specifically, one of the forms has a thousand years+ of algebra notation behind it, the ot…
Re: Django on Heroku running with Celery
#26Are there any drawbacks to this? I've been looking for a "Heroku for Django" for a few months and I just started using Google App Engine to get some of what I want. I'll go ahead and try this if it works well.
Re: Django on Heroku running with Celery
#27I feel like the title of this post would make someone over the age of fifty's head explode.
Re: Django on Heroku running with Celery
#28Also, how much RAM can a process use? What happens if I run Redis and fill it up with "a lot" of data?
Re: Django on Heroku running with Celery
#29Are there any drawbacks to this? I've been looking for a "Heroku for Django" for a few months and I just started using Google App Engine to get some of what I want. I'll go ahead and try this if it works well.
If you want a dedicated cloud hosting platform that works really well with Django you could do worse than try http://www.ep.io/ (currently invite only, but really good service).
Re: Django on Heroku running with Celery
#30Are there any drawbacks to this? I've been looking for a "Heroku for Django" for a few months and I just started using Google App Engine to get some of what I want. I'll go ahead and try this if it works well.
The [good / bad] news for you is: you [won't have to / can't] use the AppEngine High Replication Datastore. It's also worth mentioning that unlike AppEngine the Heroku stack is a unix based environment (call "heroku run bash" and boom, you have shell access) and its components are all open sourced, so it should be relatively easy to move from there to a VPS if you ever need to. Other than that, Heroku comes from mult…