lincolnloop / django-best-practices Goto Github PK

Jannis says so, https://twitter.com/jezdez/status/245992841820635136

There's some apps that (for the most part) everyone uses: south, celery, easy-thumbnails, etc. We should point people in that direction.

See also: http://news.ycombinator.com/item?id=4515257

Request via email:

I appreciate your best practices info, but I wish you had an Apache httpd server section.

Thanks for your efforts.

A great overview of best practices in developing and deploying with Django. Bookmarked.

Smashing Magazine

If you're a web developer, you should know about this.

Mike Loukides

This is close to being a direct channel to my brain. Perfect!

Daniel Greenfeld (pydanny)

As noted on Twitter earlier i was wondering if the recommendation for setting up nginx should come with a warning to make sure the root var in the nginx config is pointing to a directory with your static files not the root of your django app.

Your config uses the handy try_files shortcut:

root        /var/www/domain.com/;

# Check if a file exists at /var/www/domain/ for the incoming request.
# If it doesn't proxy to Gunicorn/Django.
try_files $uri @django;

This is fine if domain.com has your static files but if you deploy a standard (instead of your suggestion from another part of the best practices) django app layout on your server it will make any python file, including your settings, available for download.

For instance if this is (part of) your app layout:

/var/www/domain.com/
    |- manage.py
    |- settings.py
    |- static/
        |- style.css

A call to http://domain.com/static/style.css will load fine and make it look like you did a fine job deploying following best practices. While at the same time http://domain.com/settings.py will start a download of your settings.py file.

Obviously this is bad and you should not point the root to your app but i'm betting people will read that tip which they will find when googling and then do exactly this...

Would be nice to have this all available as in .mobi / .epub format.

Heroku or ElasticBeanstalk?

http://news.ycombinator.com/item?id=4515257

From http://lincolnloop.com/django-best-practices/apps/modules/urls.html

Should have a name attribute so they are reversible; APP_MODEL_VIEW, for example blog_post_detail or blog_post_list.

May I suggest:

Should have a name attribute and a namespace so they are reversible and unique to the application, for example blog:post_detail or blog:post_list.

References:
https://docs.djangoproject.com/en/dev/topics/http/urls/#defining-url-namespaces
https://docs.djangoproject.com/en/dev/topics/http/urls/#topics-http-reversing-url-namespaces

Please describe how to schedule scripts for simpler tasks. E.g. using BaseCommand. A lot of people suggest setting up urls to start the script, having an external script that import settings and many other complex things. The craziest thing I've seen (but probably useful for some cases) is to have the regular requests from google-bots invoke scripts... That's why I think it's a good thing to suggest managment commands when they're so easy and integrates nicely with your apps.

I was wondering if the best practices described in this repo are already implemented on the Cookiecutter Django project? If not, maybe it is a good idea to do so.