Live data from Hacker News

Django on Heroku running with Celery

gist.github.com

31–40 of 47 posts

Re: Django on Heroku running with Celery

#31

Heroku, AppHosted, DotCloud, ep.io, Gondor.io, DjangoZoom, Google App Engine. Looks 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…

All the ones that support Django out of the box, are all in private beta I believe. So the market is starting to warm up to Django, but still not open for sale. Hopefully they all get through private beta and release, because competition is good for the market.

Re: Django on Heroku running with Celery

#32

Earlier quoted context omitted.

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…

Just make your point and stand by it, don't say it unless you mean it.

To be clear, it was a intended helpful comment with the point that the argument /exists/, an attempt to explain why one would do such a thing. Whether you or I support it or not is irrelevant.

Unless you are arguing that the idea should not even be discussed, downvotes are malicious. The mere mention of an idea should not be attacked.

Re: Django on Heroku running with Celery

#33

Earlier quoted context omitted.

Just make your point and stand by it, don't say it unless you mean it.

To be clear, it was a intended helpful comment with the point that the argument /exists/, an attempt to explain why one would do such a thing. Whether you or I support it or not is irrelevant. Unless you are arguing that the idea should not even be discussed, downvotes are malicious. The mere mention of an idea should not be attacked.

"Yep. It could be argued that the first is more readable though" -> I agree with you that this vote should not have been down-voted. I feel like the down-vote was more of a "I think what you said is wrong" rather then a "this comment was useless or misplaced".

However, I feel like the following replies coming from you were unnecessary aggressive.

In your first comment, after you saw that people didn't understand the meaning, I think it would have been better to edit it and explain - without being aggressive - what you intended by "more readable".

Re: Django on Heroku running with Celery

#34

Only http traffic is routed to your web processes so a different protocol (I don't know, IRC) won't be routable to one of your deployed processes, correct? Also, how much RAM can a process use? What happens if I run Redis and fill it up with "a lot" of data?

how much RAM can a process use? What happens if I run Redis and fill it up with "a lot" of data?

From http://devcenter.heroku.com/articles/how-much-memory-does-a-... : Each dyno has 300MB of memory. If your process uses more than 300MB, the system will automatically kill your dyno and insert an entry into your logs.

Re: Django on Heroku running with Celery

#36

Earlier quoted context omitted.

Just make your point and stand by it, don't say it unless you mean it.

To be clear, it was a intended helpful comment with the point that the argument /exists/, an attempt to explain why one would do such a thing. Whether you or I support it or not is irrelevant. Unless you are arguing that the idea should not even be discussed, downvotes are malicious. The mere mention of an idea should not be attacked.

Communicate in way that will convey the meaning you desire to others. Everything else is self-indulgence and solipsism.

It's your responsibility to make yourself understood, not ours.

Re: Django on Heroku running with Celery

#38
post #23

Are 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…

If you like the idea of "Heroku for anything", I encourage you to try the original: dotCloud has been running a similar platform for almost a year now.

We're flattered to see everyone shift gear and try our approach. But we like being one generation ahead - and we have a few announcements up our sleeve, too.

Re: Django on Heroku running with Celery

#39

Are 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.

dotcloud (http://www.dotcloud.com/) has been my go-to django (and everything) hosting. They seem to hand out invites pretty quickly, esp if you tweet them (http://docs.dotcloud.com/faq/#i-need-a-beta-invite-right-now).

I signed up for all the betas of django hosting places a while ago and dotcloud was the only one I heard from. I'm pretty sure they're YC too.

Re: Django on Heroku running with Celery

#40
post #33

Earlier quoted context omitted.

To be clear, it was a intended helpful comment with the point that the argument /exists/, an attempt to explain why one would do such a thing. Whether you or I support it or not is irrelevant. Unless you are arguing that the idea should not even be discussed, downvotes are malicious. The mere mention of an idea should not be attacked.

"Yep. It could be argued that the first is more readable though" -> I agree with you that this vote should not have been down-voted. I feel like the down-vote was more of a "I think what you said is wrong" rather then a "this comment was useless or misplaced". However, I feel like the following replies coming from you were unnecessary aggressive. In your first comment, after you saw that people didn't understand the…

Logically, yes. However I found multiple quick downvotes over a very benign statement rude and reacted in kind.

People would like to think they don't matter, but it is the same as walking into a room and punching someone in the arm. If I had made some horrible statement it might make sense.

Post reply on HN