From: Dan Loewenherz <dloewenh...@gmail.com>
Date: Thu, 27 Sep 2012 09:51:52 -0700
Local: Thurs, Sep 27 2012 12:51 pm
Subject: Feature request: collectstatic shouldn't recopy files that already exist in destination
This is a feature request / proposal (one which I'm willing to build out,
I run a consulting business that helps small startups build initial MVPs.
Now, Django has an awesome mechanism for making sure static assets are up
The problem I've run into is that collectstatic copies all files,
As I wrote in the trac ticket (https://code.djangoproject.com/ticket/19021),
I currently solve this problem by creating a file containing metadata of
> all the static media at the root of the destination. This file is a JSONI'll contribute the patch. I know there is not a lot of time before the
> object that contains file paths as keys and checksum as values. When an
> upload is started, the uploader checks to see if the file path exists as a
> key in the dictionary. If it does, it checks to see if the checksums have
> changed. If they haven't changed, the uploader skips the file. At the end
> of the upload, the checksum file is updated on the destination.
feature freeze, but I'm willing to make this happen if there's interest.
If we don't want to change behavior, perhaps adding a flag such as
All the best,
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.