On Nov 4, 3:06 am, Jannis Leidel wrote:
> Ok, thanks for your input, would you mind creating a ticket describing the
> discrepancy in more detail? I thought the how to [1] explains enough of
> purpose of the app, so any further input would be much appreciated.
>
> > I'd be glad to help, but I'm
On 04.11.2010, at 00:55, Brian Neal wrote:
> On Nov 3, 4:12 am, Jannis Leidel wrote:
>>
>> No, MEDIA_* and STATICFILES_* settings aren't the same, the former is for
>> user generated content (like file uploads), the latter for general static
>> files your site needs to work (such as css/js fil
On Nov 3, 4:12 am, Jannis Leidel wrote:
>
> No, MEDIA_* and STATICFILES_* settings aren't the same, the former is for
> user generated content (like file uploads), the latter for general static
> files your site needs to work (such as css/js files). The distinction is also
> well described in t
On 31.10.2010, at 23:06, Ryan wrote:
> I track trunk while developing new projects, and I just picked up the
> new contrib.staticfiles app. I was disappointed how repetitive and
> redundant the configuration is. I already have MEDIA_ROOT and
> MEDIA_URL defined, so now I have to add
>
> STATICF
I've been a staticfiles user for a while, let me explain my normal setup,
and one where it's a bit more complicated.
PROJECT_ROOT = /path/to/project
MEDIA_ROOT = PROJECT_ROOT/site_media/media
STATICFILES_ROOT = PROJECT_ROOT/sitemedia/static
PROJECT_STATIC (not an actual setting) = PROJECT_ROOT/st
I track trunk while developing new projects, and I just picked up the
new contrib.staticfiles app. I was disappointed how repetitive and
redundant the configuration is. I already have MEDIA_ROOT and
MEDIA_URL defined, so now I have to add
STATICFILES_ROOT = MEDIA_ROOT
STATICFILES_URL = MEDIA_URL
