Live data from Hacker News

Heroku clone for Django?

djangy.com

61–62 of 62 posts

Re: Heroku clone for Django?

#61

Earlier quoted context omitted.

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

Sure. I doubt you'll get much out of it, but I'm still quite curious what your impression will be. http://pastebin.com/Q970rYaH If it helps, "li" is my current project's code name. The vast majority of the code is concerned with configuring a fresh Linode, not pushing recent changes (for that, see the rf and stage functions, and the functions they call). I hate system administration. The only way I could make myself…

thanks!

Re: Heroku clone for Django?

#62
post #26

Earlier quoted context omitted.

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

I haven't tried djangoappengine, but it seems possible it would abstract away most of the datastore-related stuff and make the admin work.

Not true, unfortunately. For example, creating objects and deleting them uses a different method (put instead of save). There are tiny syntax differences, also.

Not to mention the fact that designing an information schema for a SQL database is quite different from designing an info schema for a hash-table like datastore (which appengine has).

Post reply on HN