Live data from Hacker News

Heroku clone for Django?

djangy.com

21–30 of 62 posts

Re: Heroku clone for Django?

#23

How do they plan to compete against Google App Engine? http://www.allbuttonspressed.com/projects/djangoappengine

Maybe by not requiring any modifications of Django to get the basics running? Allowing standard databases? Or even the popular thing lately - by not being Google.

Or maybe they'll enable more stacks? Pylons shouldn't be that hard to plug in once you have Django deployments working. And since they reached 1.0 lately...

Re: Heroku clone for Django?

#25

Earlier quoted context omitted.

I regularly use Fabric. After deploying a couple of projects with it, I have come up with a standard deployment layout and stack. Now its as simple as "fab deploy" and "fab revert". Thank you fab!

Same here, except I've set things up so that any changes I make to my project are automatically synced instantly to a live staging domain, and I don't have a revert command (although I do back up copies of previous deployments). I also keep apt and pypi dependencies in project-local config files and have a refresh command that updates those packages on both the remote and local machine along with some other stuff. I…

would any of you share these files and your setup? I'd love to have a look into them.

Thanks!

Re: Heroku clone for Django?

#26

How do they plan to compete against Google App Engine? http://www.allbuttonspressed.com/projects/djangoappengine

App Engine is a pain in the ass, and I wouldn't recommend it to anyone. Heroku is so simple to use that I've many times felt that someone needs to build a Heroku for Python.

The only thing really wrong with App Engine is the datastore:

- It's very different than anything you've come across before - The docs are not sufficient for it's complexity. You end up having to read lots of blogs and watch lots of videos to figure it out. - It is ridiculously difficult to learn (one of the hardest things I ever had to do) - Important parts of your stack won't work, like Admin - You can't just add the fields you like to an object. Instead you need to meticulously plan _how_ your data is going to be accessed. This is exactly the wrong thing for a startup, since you can't get up and running fast. - You can't iterate fast, because any schema change is very risky and very slow. - If you don't get everything exactly right, your app will be very slow. - There isn't much in the ecosystem.

By contrast, none of these are true for Heroku.

There are some things that are pretty good about App Engine:

- the tools are pretty good. Not as good as Heroku, but good. - the billing is spot on. They give you about $1 per day of free stuff, which can maintain a site with hundreds of thousands of users. And it's pretty cheap from there on. - They scale it automatically. On Heroku, it's really hard to tell how many "dynos" (whatever the hell that is) you need, except by trial and error. I would expect that nearly all Heroku apps are overprovisioned. App Engine just nails the scaling - it happens automatically, and you specify a maximum amount to pay per day, with lots of different dials to control it more precicely if you like.

I hope Djangy takes the best of both worlds.

Re: Heroku clone for Django?

#27
post #22

I wonder why Dave Paola (apparently admin at djangy according to DEBUG view at http://djangy.com/postreceive ) used room606 instead of his regular account endlessvoid94 for submitting this.

Because he doesn't want to be outed, for whatever reason. Outing someone by calling out their real name is a dick move. It used to be that HN recognized the occasional need for stealth pre-launch, instead of this braggery.

(Disclaimer: same thing happened to my company when we pre-launched.)

Re: Heroku clone for Django?

#30

How seriously can you take a service if developers forgets to disable the DEBUG flag :) http://djangy.com/admin

Use of SQLLite too - does that scale and perform well against something like postgres?

I think what we're seeing here is an email/hype-grabbing attempt with an interesting vision, using the Heroku name for leverage.

Would like to see it materialise, but they really should have hardened something as simple as a signup form. I've emailed the admin telling him to lock it down.

Post reply on HN