Hi all, This is to initiate a discussion on whether we should add a new overwrite method to collectstatic.
Although I agree that we should careful in adding new features, I think this one is pretty useful. Here is why: - We want the files in STATIC_ROOT to be replaced even if the one there is newer. Currently I don't see a way to do this apart from using --clear which deletes the entire directory, where other apps could be writing too. We could implement overwrite where it does a filecmp and then overwrites. - The clear method deletes the files irrespective of where they are, an accident could mean that data could be lost for ever. In one instance our production box had STATIC_ROOT point to a folder in the app accidentally, then collectstatic was not fetching a file from a sub app which was linked to the main project, we ran collectstatic --clear and it deleted the static folder of the main project which had some base css/js files. This could have brought down production for a while if not for a caching mechanism. - Django should be able to run in a safe mode where no unintended side-effects should happen. What are your thoughts on this? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0299af3f-c45a-4e51-b5ae-11b71f84b83d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
