I've just started using Dotcloud for some Django projects, and I just want to say I absolutely LOVE how easy it is to set up apps, databases, etc, despite the beta state and the limited documentation at the moment. Highly recommended.
Thanks for the kind words! Since the DotCloud team is furiously refreshing this page, now is a good time to ask questions and give feedback! We also have a brand new community forum: http://support.dotcloud.com/forums
Amen. I was just asked to give a testimonial by one of their product team, and I damn near tripped over myself trying to respond as quickly as I could.
I've had experience with a number of the 'heroku for Django' startups going around, and while I don't have any complaints against any of them, dotcloud is KILLING in this space.
The best part, to me, is not having to mess about with various components -- I was able to put together a wordpress/mysql stack for one project, Django/Postgres for another, and Flask/mysql for another with the same interface, the same ease of use, and the same instant gratification.
Exactly, it really has become the go to place for my pet projects as well as professional projects. Regardless of what platform/backend mix I choose, Dotcloud usually has it.
I don't have to worry about forcing myself to use RoR because there was only Heroku anymore.
Same here. We just launched noteleaf.com (YC W2011) about two weeks ago, and migrated over to dotcloud this past weekend. Due to my naiveness with some key infrastructure, our processing times was over 3 hours when we launched the first time. With their premium support, Dotcloud's team helped me work through and reduce the processing time to ~20 minutes, and the start times for each worker was reduced form 44 secs to milliseconds, in preparation for our second launch today.
It's because of Dotcloud that I'm not currently in the pits of despair and can concentrate on my application and my users...and commenting on HN.
Two quick updates I'm going to put in the blog post: Know that the server times are in UTC, so your cron schedule needs to be in UTC. Also you need the RAILS_ENV to be set to production in the scheduler as well as the worker.
10 comments
[ 3.5 ms ] story [ 24.9 ms ] threadAlso happy to give out invites to fellow HNers!
I've had experience with a number of the 'heroku for Django' startups going around, and while I don't have any complaints against any of them, dotcloud is KILLING in this space.
The best part, to me, is not having to mess about with various components -- I was able to put together a wordpress/mysql stack for one project, Django/Postgres for another, and Flask/mysql for another with the same interface, the same ease of use, and the same instant gratification.
It really is gold.
I don't have to worry about forcing myself to use RoR because there was only Heroku anymore.
It's because of Dotcloud that I'm not currently in the pits of despair and can concentrate on my application and my users...and commenting on HN.
I can't recommend them enough.