I like the idea. But make sure to differ from what AppEngine offers or you have a very strong opponent.
Heroku clone for Django?
51–60 of 62 posts
Re: Heroku clone for Django?
#52So, this is my site. Yep. I forgot to turn debug off. Yep. And i'm using sqlite3 to accept email addresses. Yep. I can assure you the quality of the ACTUAL project is far better :-) I have a working prototype and am working my ass off to get something scalable up and running asap. keep checking back for details!
Regardless of the criticisms, if you need another beta tester, you'll find my email in your sqlite database. ;-)
Seriously though, best of luck, and godspeed.
Re: Heroku clone for Django?
#53Is it just Django, or will other Python frameworks work?
Seems like it wouldn't be hard to support any WSGI application...
Re: Heroku clone for Django?
#54Earlier quoted context omitted.
While I do agree that the App Engine datastore does require for some planning above what you're used to from a traditional RDBMS, I think it really just reflects a learning curve that comes with any new technology: as you use it more often, you get better at it. I think calling App Engine a pain in the ass and that you wouldn't recommend it to anyone is a bit over the top.
No, I truly meant it. Everything related to the datastore is difficult and tedious. Goodbye to incremental development, goodbye to knocking out a feature in an hour. Every single change you make has to be planned. Adding a field to an "object"? Where do you use that object? Is there somewhere that you don't use that field which becomes too slow? How are you going to migrate that new field? There aren't tools to help…
I'd have to agree that Django on appengine is a big pita for the reasons you mentioned. Django is a large framework, and was simply not designed with interchangeable backends in mind. Getting it to work either requires a lot of black magic monkey-patching or foregoing the majority of built in features.
On the other hand, I have found the datastore api (and most of the other apis) to be well designed. It works very well with lighter frameworks such as tornado.
Re: Heroku clone for Django?
#55Earlier quoted context omitted.
To be fair, you wouldn't need much more than SQLite to gather emails. It's more than sufficient (I would say it's absolutely amazing for most use cases, but the one thing I am not sure about is how well it handles concurrency, if at all). I tried SQLite for a few things, and it has always come out a champ. I would not hesitate to use it for most of the semi-static websites I make (web apps would be pushing it), if I…
SQLite is a file and thus uses file-level locking and does not have row-level locking. Data can not be read the same time anything is being written, so it is usually not great for multi-user applications or web applications. Development, or 1-3 user web app it should perform OK. It doesn't scale and you will get db locks and retries if its under too much load. To speed this up (if you must use SQLite), use a solid st…
http://linux.die.net/man/2/fcntl
actually it could use row-level locking since it uses row-oriented storage and fcntl locks can be applied to a set of bytes within a file. it could also do file-level locking on tempfiles with names derived from the table name and primary key of the row.
anyone with actual knowledge of it care to chime in with what it does do?
Re: Heroku clone for Django?
#56Earlier quoted context omitted.
SQLite is a file and thus uses file-level locking and does not have row-level locking. Data can not be read the same time anything is being written, so it is usually not great for multi-user applications or web applications. Development, or 1-3 user web app it should perform OK. It doesn't scale and you will get db locks and retries if its under too much load. To speed this up (if you must use SQLite), use a solid st…
http://linux.die.net/man/2/fcntl actually it could use row-level locking since it uses row-oriented storage and fcntl locks can be applied to a set of bytes within a file. it could also do file-level locking on tempfiles with names derived from the table name and primary key of the row. anyone with actual knowledge of it care to chime in with what it does do?
I have actual knowledge of it. The product I work on uses it as the production database because we distribute the software as a desktop application (and MySQL has licensing issues).
It COULD do row level locking, but it doesn't. SQLitening is the closest thing to performant SQLite you will get. And it only runs on Windows.
Re: Heroku clone for Django?
#57How 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 fig…
It sounds like your problem with App Engine is that you're Django. Yeah, Django is not built for the App Engine data store, so why not use something that is? I've used the Tipfy and Flask frameworks (both are a thin layer on top of Werkzeug), and they experience has been great.
Re: Heroku clone for Django?
#58Earlier quoted context omitted.
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!
Sure. I doubt you'll get much out of it, but I'm still quite curious what your impression will be.
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 configure my server was by writing a script to configure it for me.
Re: Heroku clone for Django?
#59How 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 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.