Support for STATICFILES_DIRS about django-sass-processor

[AndreasBackx]

As far as I'm aware the output will be stored in either the static root or the specified sass root. I should've been more specific and that might be because this was very late (or early), but my idea was to output them in a path relative to the input SCSS-file.

root/
    app/
        scss/
            app.scss
        static/
            css/
                app.css
    app2/
        scss/
            app2.scss
        static/
            css/
                app2.css

Instead of:

root/
    app/
        scss/
            app.scss
    app2/
        scss/
            app2.scss
    static/
        css/
            app.css
            app2.css

app/static, app2/static, app/scss, and app2/scss would then be in STATICFILES_DIRS. Perhaps make SASS_PROCESSOR_ROOT possible to be a path relative to the source SCSS file?

[jrief]

But it does – at least in my setup.
I'm currently using two apps relying on sass-processor and they both are shipped with their own ...scss files.

[Auroch]

Do you have find a solution for obtaining this behaviour ?

[jrief]

I always keep my compiled files out of my projects, hence my STATIC_ROOT points onto that external folder. This prevents to have a mixture of hand written and autogenerated files. This also is the reason why you need STATICFILES_FINDERS = (..., 'sass_processor.finders.CssFinder', ...).

[jrief]

@AndreasBackx can I close this?

[AndreasBackx]

Ya, it's not that big of a deal.