, or 'no' to cancel:
>
> Maybe we can tweak the message if it's not clear, but adding more code
> logic to try to make the error message "smarter" seems overkill to me.
>
> On Wednesday, October 29, 2014 1:41:56 PM UTC-4, Prathik Rajendran M wrote:
>>
ly empty) destination directory for collecting your static files
> from their permanent locations into one directory for ease of deployment;
> it is *not* a place to store your static files permanently."
>
> On Wednesday, October 29, 2014 12:55:29 PM UTC-4, Prathik Rajendran M
> wrot
ders, my analysis of the issue and why I don't think it's
>> appropriate can be found on the ticket where the idea was first raised:
>> https://code.djangoproject.com/ticket/23724
>>
>> On Wednesday, October 29, 2014 11:34:02 AM UTC-4, Prathik Rajendran M
>&g
e messed up".
> On 29 Oct 2014 16:05, "Tim Graham" >
> wrote:
>
>> For other readers, my analysis of the issue and why I don't think it's
>> appropriate can be found on the ticket where the idea was first raised:
>> https://code.djangoprojec
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
