Issue with S3 storage using django-storages about django-sass-processor

[dgourley]

@cdriehuys you need to define your own storage class and define the base_url for your s3 configuration. Something like....

In your yourapp/settings.py set your static files storage:

STATICFILES_STORAGE = 'yourapp.storage.YourStorage'

Then define it in yourapp/storage.py

from storages.backends.s3boto import S3BotoStorage
class YourStorage(S3BotoStorage):
base_url = 'yourbucket.s3.amazonaws.com'

[jrief]

@cdriehuys Please provide a pull request fixing this. Otherwise, please contact me on my private email address.

[cdriehuys]

Sorry for the delayed response. Unfortunately I don't have the time to make a pull request for this currently, but I appreciate you taking the time to look at this issue.

[jrief]

@cdriehuys If you can fund this feature, I can do it for you. Currently I have no plans to use AWS with S3, so it's not on my personal "to do" list.

[jrief]

@dgourley I haven't been aware of this. Could you please add this to the README and open a pull request.

[dgourley]

@jrief will do. I just ran into this issue last night and found this as a workaround. Seems S3BotoStorage doesn't have base_url defined... easy enough to add the configuration. If you are using s3 you probably are defining a storage anyway to enable caching, manifest files, etc.

[cdriehuys]

@dgourley Thanks for the workaround. I avoided the issue by switching to a different build process, but I'll definitely use that solution on future projects.

[jrief]

@cdriehuys Can this issue be closed then?

[cdriehuys]

Yes. I think the provided solution is easy enough to follow that this doesn't need to be fixed in the package itself.

[AlBlanc]

Actually the issue is: django-sass-processor is trying to read the base_urlof each django apps storage classes.

But base_url is an attribute of FileStorage, so django-sass-processor assumes we must use a FileStorage and block us from using some other storage classes like one provided by django-storages which override Storage class (which is FileStorage superclass)

I really think a quick fix could help a lot of people. I'll try to take some time during this week to push a pull request. For the moment, i'll take the workaround above. Thank you!

[jrief]

@AlBlanc if you can fix this, it would be great. Currently I have no use-case for this, hence that's not on my priority list.