31–40 of 46 posts
Setup: * Pylons+SQLAlchemy+formencode+Mako+WSGI apps * PostrgeSQL * Nginx Tools: * Virtualenv * Fabric Best combination. Zope, Django, Web2py, web.py are just not that flexible & reliable for advanced web applications (IMHO).
database: Postgresql
server: UWSGI + Cherokee
Flask is a very nice framework, and the documentation is awesome. I've tried a lot of Python frameworks out before deciding on Flask. It's a paralyzing decision - there is just so much out there. The process of choosing a web framework is filled with information overload - from reading about the framework, dabbling with the code, and finally learning the actual framework. For the reason, I recommend going with a microframework. You learn what you need as you go. So this lead me to Flask.
Two things set Flask apart (for me) - the documentation and the extensions. Just check out the site http://flask.pocoo.org for more information. You also want to be assured that development on the framework is not just going to be dropped some day. It really feels like this framework is going places. (My initial inclination was toward CherryPy, but the documentation is bad. After all these years.)
My dev work is mostly done on Windows, and for an IDE I've taken to using JetBrain's PyCharm. (I'm primarily a .NET developer, and I find it more convenient to use Windows to avoid context switching. The fact that I deal with the massive and all-encompassing .NET is also a major reason I went with a Python microframework). On Linux, I can get by with Emacs.
Using Ubuntu in production environment.
- TextMate - Google App Engine - http://www.tipfy.org (GAE specific framework)
I hate App Engine, but unfortunately I will probably be doing at least a few more projects on it, so thanks for the link to tipfy, maybe it'll help.
http://www.franciscosouza.net/2010/08/flying-with-flask-in-g...
Django. Disclaimer: We're about to launch Djangy.com, so my opinion is obviously biased.
Other than that I'd like if you could also give a sense of expenses that I might run into if I deploy my app on djangy. The details in terms of pricing are lacking there.
Just some feedback. I know it's in private beta. All the best.
Django. Disclaimer: We're about to launch Djangy.com, so my opinion is obviously biased.
I happen to have a djangy account and I tried some of it few days back. I made a simple hello world app and deployed it but it took longer time to go live than I had anticipated, esp. in comparison to Appengine. Other than that I'd like if you could also give a sense of expenses that I might run into if I deploy my app on djangy. The details in terms of pricing are lacking there. Just some feedback. I know it's in pr…
Would you mind emailing me at dave@djangy.com? I'd like to ask you some details about which app was yours, and what exactly your experience was. We're about to roll out a TON of new changes within the next few days, and we'll be inviting quite a few more users into the beta program. I want to make sure we're covering all the bases and keeping users happy.
Thanks :-)
framework: Flask database: Postgresql server: UWSGI + Cherokee Flask is a very nice framework, and the documentation is awesome. I've tried a lot of Python frameworks out before deciding on Flask. It's a paralyzing decision - there is just so much out there. The process of choosing a web framework is filled with information overload - from reading about the framework, dabbling with the code, and finally learning the…
Deadly simple, but still everything you need :)
PostgreSQL + Mongo + Memcache
Apache + wsgi