Hacker News new | comments | show | ask | jobs | submit login

Sorry to hear things that you're having trouble with dotCloud. A couple quick questions:

First, which requirements are you putting in your dotcloud.yml? In general, pip-installable requirements should just go in a standard requirements.txt file, and dotcloud.yml should be used to describe the higher-level structure of your application (ie which service types you need).

Also, I'm not sure what you mean about "masking the debug interface", but all your Flask/WSGI and nginx logs are available with the "dotcloud logs" command, and you can also log into your service instance directly to debug using "dotcloud ssh" (in which case logs can be found in the /var/log directory). You can also certainly use Flask in debug mode, by setting "application.debug = True" in your wsgi.py

It is true that you may have trouble using the interactive, browser-based debugger with the default setup on dotCloud, then but this is a Flask limitation, not a dotCloud one. From http://flask.pocoo.org/docs/quickstart/#debug-mode: "the interactive debugger does not work in forking environments (which makes it nearly impossible to use on production servers)"

Hope that helps, and if you have any other questions, drop us a line: support@dotcloud.com

Thanks for the response! I had to facepalm at the WSGI config, I had been setting it within the app itself: it returned a 500 otherwise, which makes sense now.

Consider my one issue moot! Next time I'll read the docs better before complaining...



Any docs changes we could make to avoid others hitting the same problem?


Nope. The relevant info is literally the first warning callout on the Python guide: http://docs.dotcloud.com/services/python/

Thanks again for taking the time to set me straight on this.


Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact