#19650: Add command option to ignore error when collecting static files.
-------------------------------------+-------------------------------------
Reporter: zyegfryed | Owner: nobody
Type: New feature | Status: closed
Component: contrib.staticfiles | Version: master
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 1 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by zyegfryed):
We're talking about adding a flag like the ''-f/--force'' option from
''git add'' or ''git push''. Something that is really common and sometime
useful even if not always the way to go. But we know what we're doing when
using it.
A file can be missing because someone hasn't tested enough it's app. But
it can also occurs due to network/provider issue when uploading
to/retrieving from FTP/S3/whatever or because it has been corrupted
somehow. It happens. We have to be aware of it and the default behavior is
the right one because it warns us about it. However, Django should be able
to help us to bring back some working state - all in all, cache busting is
an option and shouldn't be a deployment blocker - letting us time to
tackle the missing file issue. That's the point of this optional flag.
--
Ticket URL: <https://code.djangoproject.com/ticket/19650#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
