Opened 4 months ago
Closed 4 months ago
#35709 closed New feature (duplicate)
Command collectstatic should relay on checksums instead of modify time
| Reported by: | Grzegorz Przybylik | Owned by: | |
|---|---|---|---|
| Component: | contrib.staticfiles | Version: | 5.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Grzegorz Przybylik | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In our project we mostly relay on containerization and packing code including their static files into containers. During upgrade we call manage.py collectstatic inside that container and our static files are uploaded to s3 bucket.
Collectstatic command to make sure if file needs replacement checks creation timestamp on destination storage and local file storage. But problem is that creation time of static files inside container are set during image creation. This causes issues in deploying older images, because of their create timestamps mentioned earlier.
My idea to fix this is to check files checksums (like md5 or sha) and using them to compare file identity.
Change History (1)
comment:1 by , 4 months ago
| Component: | Core (Management commands) → contrib.staticfiles |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
| Type: | Cleanup/optimization → New feature |
Note:
See TracTickets
for help on using tickets.
Hello Grzegorz Przybylik, thank you for taking the time to create this ticket.
I understand the goal of your proposal, but please note that this was already proposed and discussed in ticket #19021, and it was marked as
wontfixfor the reasons stated in its closing ticket:19021#comment:7.Closing as duplicate following the ticket triaging process.