-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Aymeric,
On 10/19/2011 01:07 AM, Aymeric Augustin wrote: > Collecting static files and putting media uploads in the "project > directory" (whatever that means) isn't really a best practice. In > production, the code area should be read-only for the web server > user: code goes in /usr/... and data in /var/www/... (FWIW, my +0.5 was for creating a static/ directory that would go in STATICFILES_DIRS, definitely not setting a default value for STATIC_ROOT). > In order to make deployment easier, I also recommend putting > site-wide templates and templatetags in an application, and keeping > TEMPLATE_DIRS empty, but that's a personal preference. Just out of curiosity, why would you say it makes deployment easier to put static assets and templates into an installed app, rather than using TEMPLATE_DIRS/STATICFILES_DIRS? (Templatetags are a different issue; those have to go in an app). Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6ggvQACgkQ8W4rlRKtE2fHVACg2RxqopGeAYaMReVbV/u7SkVq TuAAn1Zso3AYjGrtem6QFuhpZlq1tJS0 =OpHw -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
