Closed maria closed 10 years ago
@marianitadn
You are not alone with waiting for a pypi-update (#13, #4, #16).
But in your case, on Heroku (or any PaaS) MediaCling
is useless since your local filesystem isn't shared between the instances of your application.
Best bet is to go with something like (django-storages)[http://django-storages.readthedocs.org/en/latest/] for media-files.
For static-files, dj-static is fine since Heroku runs collectstatic
when the slug is created.
You are not alone with waiting for a pypi-update (#13, #4, #16).
Sorry, I didn't saw the one which is still open, just the other two. Maybe the fourth issue is the lucky trigger.
But in your case, on Heroku (or any PaaS) MediaCling is useless since your local filesystem isn't shared between the instances of your application.
I have one instance for my app and I use MediaCling
, and it works fine. :)
You can rely on heroku redeploying your instances (and so, deleting your media) at some point in the future :)
When running
pip install dj-static
it will install the version0.5
, and we aren't able to import the classMediaCling
. For those who want to serve media files, images, on Heroku is useful.