플라스크 프로젝트의 구조를 어찌하면 좋은가

gistfile1.md

flask proj

• http://flask.pocoo.org/docs/0.10/blueprints
• https://exploreflask.com/organizing.html
• https://realpython.com/blog/python/python-web-applications-with-flask-part-i/
• https://github.com/imwilsonxu/fbone
• https://github.com/mattupstate/overholt
  • http://mattupstate.com/python/2013/06/26/how-i-structure-my-flask-applications.html

notes

• use requirements.txt, not setup.py because it would not be a module...

trivia

• unittest directory is tests, not test
• use py.test or standard unittest module
• absolute_import를 쓰면 좋을 것 같다. 하지만 욕심인 것 같기도.
• deploy: fabric
• blueprints: app, celery-worker-mail-sender, celery-worker-google-auth, celery-worker-apns, celery-worker-apns, ...

structure

• /
  • myapp/
    • __init__.py # holds app
  • tests/
    • __init__.py
    • test_basic.py
  • requirements.txt # minimal requirements, with versions.
  • requirements-dev.txt # requirements for development (py.test, flake8, ...)
  • requirements-freeze.txt # store current working (proven) versions (from pip freeze)