Hi, DotCloud'er here! Those timeout errors are pretty common, and we are working very hard to reduce them. Almost all operations should be idempotent - meaning

Hi, DotCloud'er here! Those timeout errors are pretty common, and we are working very hard to reduce them. Almost all operations should be idempotent - meaning that you can repeat them without any danger. Basically: if the 1st time didn't work, the 2nd time will do; if the 1st time did work, the 2nd time won't do anything. We got a fairly massive growth, and a lot of internal components required to be upscaled much earlier than planned. As we rewrite, optimize, and weed out bugs out of thos components, the timeouts will disappear, and the platform will be faster as a whole. Just so you know - we are using the "eat your own dog food" principle as much as possible. API, website, docs... are all using the DotCloud platform itself, and we generally don't need escalated privileges to debug stuff. I think we need to be more explanatory about the various ways to inspect logs and debug code, since there is a lot more than meets the eyes :-) I'm curious about how you feel that we are "more restricted than the Heroku environment"; I would really feel compelled to fix it in any case! All the best,