4 ms·
Heroku clone for Django?
- lzw 16y agoIntersting!
- twigil 16y agocan't wait for trying it!
- yurylifshits 16y agoNever write form confirmations ("Thanks for your email") in red color. Looks like a warning. If a form is processed correctly, it should be black or green. I hope that usability of djangy service will be better. Can't wait to try it :) Btw, isn't Heroku itself planning anything for Django?
- jedc 16y ago> Btw, isn't Heroku itself planning anything for Django? Has that ever been mentioned or rumored before? Is that even feasible given Heroku's technology stack?
- _chap 16y agoPure speculation, but they've taken funding and seem eager to branch out. I think we'll see more than ruby hosting from them in the near future.
- ezl 16y agoI was throwing around startup ideas and I emailed them in late june 2010 to ask if they were considering it. The response was quite clear that they had no plans to enter the Django market.
- jedc 16y agoThat's what I'd expect. They're only still in the early market penetration stage of the Ruby market; it doesn't make a whole lot of sense to complicate their product offering. (Particularly when App Engine is available for Python/Java.)
- klaut 16y agoFinally it arrived :) I love Heroku and was looking for something similar for Django for ages now. Can't wait to give it a try!
- johanhil 16y agoSounds like a contestant in the AWS Startup Challenge.
- nudge 16y agoIs it just Django, or will other Python frameworks work?
- pbiggar 16y agoThey really need to support more than Django. The Python world isn't centered around one web framework, the way Ruby is.
- mitkok 16y agoActually, Heroku supports any rack application - that means most of the ruby web frameworks.
- JshWright 16y agoSeems like it wouldn't be hard to support any WSGI application...
- hasenj 16y agoWill it work for Flask? Any plans? http://flask.pocoo.org/ http://flask.pocoo.org/
- the_mitsuhiko 16y agoHopefully it will work with any WSGI application because even Django applications might use WSGI components and thus have a custom WSGI application object.
- ruby_rocker 16y agoHow seriously can you take a service if developers forgets to disable the DEBUG flag :) http://djangy.com/admin http://djangy.com/admin
- bfirsh 16y agohttp://djangy.com/signup http://djangy.com/signup Oh dear.
- phoenix24 16y agomust to be fixed quickly, that's a serious error.
- ruby_rocker 16y agoYeah thats the problem with deploying "by hand". Maybe this python guys should use Capistrano for this things :)
- spahl 16y agoFabric is nice too and it's in python (http://docs.fabfile.org/0.9.1/ http://docs.fabfile.org/0.9.1/).
- neeleshs 16y agoI 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!
- Emouri 16y agoI'm looking to optimize my fab setup, feel like sharing your fabfile.py?
- astrofinch 16y agoSame 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 think I might have overengineered things a little.
- xulescu 16y agoWould be nice if there were something like this (like Heroku) for Java. I know that there are several "cloud" solutions for Java, but I haven't found something as simple to manage/extend/deploy like Heroku so far :(.
- phoenix24 16y agoyeah there are, http://www.stax.net/ http://www.stax.net/ for Java EE developers. another, https://www.playapps.net/ https://www.playapps.net/ for play apps., those written using the playframework.
- xulescu 16y ago> http://www.stax.net/ http://www.stax.net/ I used Stax during beta, and it's nice, but it's no near the Heroku ease of use (puls it's little helper Nezumi http://nezumiapp.com/ http://nezumiapp.com/ when on the way). With very small restrictions, one can install anything on Stax, so it's very flexible, but just not that easy to use as Heroku'. > another, https://www.playapps.net/ https://www.playapps.net/ for play apps. Unfortunately Play framework is not based on a servlet container (something that 99% of java webapps are using).
- astrofinch 16y agoHow do they plan to compete against Google App Engine? http://www.allbuttonspressed.com/projects/djangoappengine http://www.allbuttonspressed.com/projects/djangoappengine
- viraptor 16y agoMaybe 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...
- pbiggar 16y agoApp 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.
- stwe 16y agoI wonder why Dave Paola (apparently admin at djangy according to DEBUG view at http://djangy.com/postreceive http://djangy.com/postreceive ) used room606 instead of his regular account endlessvoid94 for submitting this.
- pbiggar 16y agoBecause 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.)
- room606 16y agoI have no idea who Dave Paola is. I saw it posted over on coder.io and I thought it might be of interest
- endlessvoid94 16y agoI didn't submit it :-)
- pdelgallego 16y agoI really would love to see this for clojure or smalltalk.
- njl 16y agoI've been working on my Heroku for Django (or Python more generally) for a month or two now. It's good to see somebody else thinks this is a good idea.
- StavrosK 16y agoHow does it work? How do you handle persistence and parallelism?
- njl 16y agoThe front end dispatches requests to a Varnish, which is in front of a router that queues up requests and sends them to available copies of the desired application. Persistence is Postgresql, and delayed and scheduled jobs are handled by celery over RabbitMQ. My number one goal is to provide a deployment environment with as few additional restrictions on the developer as possible.
- StavrosK 16y agoThat sounds quite good! So most of the parallelism is on the view processing layer? Is the postgres setup parallelised as well?
- ramidarigaz 16y agoI would love to hear more about this. I'm currently in the middle of a Django app, and this would be a godsend. I like doing sysadmin stuff, but there's no way I will have time in the next year. If you guys can pull this off, I will be a very happy customer.
- endlessvoid94 16y agoSo, 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!
- bmelton 16y agoRegardless 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.
- js4all 16y agoI like the idea. But make sure to differ from what AppEngine offers or you have a very strong opponent.