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 I just forget the Apache VirtualHost config details, as I may never need that again?
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.
I thought Heroku only suppoted Ruby and node.js. Can someone explain what is going on here? Does it run arbitary executables, but it handles Ruby in some more powerful way?
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?
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 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.
That is pretty exciting. I moved to App Engine from EC2 because I didn't want to spend that much time managing the stack. I'm going to go try Heroku now.
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.
Dotcloud looks very interesting, but to me it's hard to consider next to strong competitors that have established their pricing... That said I'm very looking forward to see the dotcloud pricing announced.
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).
Slight OT: Is it just me or non-Ruby/NodeJS no longer works on Cedar stack?
Cleaning up...
-----> Discovering process types
! Heroku push rejected due to an unrecognized error.
! We've been notified, see http://support.heroku.com if the problem persists
1) The first statement basically says: Add 2 to x, while the second says: Take x, add 2 and add that to x.. Which is one more step.
2) When a variable is repeated multiple time, I always read the line multiple time to make sure there is no error. For instance, in english "On the screen, there there is a xyz". I'll stop and read that sentence a couple of time to try to understand it.. and then realize it's an error. Likewise, when I see x = x + 2, I think "Is it a mistake?" I.e. did the author wanted to write: y = x + 2.. if not, why does he repeat himself?
However, I'm interested in knowing in what you find it more readable :) ?
1) "Take x, add 2 and add that to x" the second add should be "set x to that".
"Which is one more step." It is the same amount of steps, just a difference in how it is represented to the end user.
2) Hmm, never thought about that type of connection before. In my experience I had many years of "x = x + 1" in both Algebra class and when first exposed to Basic programing. I didn't encounter C (first exposure to extended operators) for at least another decade.
Whenever I see such an assignment statement I visualize this in my head...
x = x + 1
x = 5 + 1
x = --> 6 <-- (woosh)
x <---6 (woosh)
(6) (thud)
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 other does not. I made no statement over whether pro programmers would find it confusing, but on the readability count, analogues to mathematics win.
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".
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.
It was a simple sentence. While I'd like for people to understand as well as possible, I'm not going to write defensive paragraphs every comment to prevent others from projecting their bias(es) onto my words and/or jumping first to negative conclusions.
It's no way to live and would be impossible anyway, how to know in which direction todays random replier will hijack my comment?
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 I just forget the Apache VirtualHost config details, as I may never need that again?