You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.
I'm using S3 with ManifestFilesMixin (it doesn't make sense to use S3 for staticfiles without it since invalidation becomes extremely complex and costly).:
fromdjango.contrib.staticfiles.storageimportManifestFilesMixinfromstorages.backends.s3boto3importS3Boto3StorageclassMyStaticStorage(ManifestFilesMixin, S3Boto3Storage):
"""Storage that uses S3 and hashes in filenames to avoid caching issues."""
However, collectfast does not properly collect staticfiles. The manifest is missing, and no files are correctly copied onto the storage / bucket. There's no error though, and lots of processing is done for 2:45m.
I'm guessing that collectfast makes some [wrong] assumptions regarding the underlying setup, but I can't quite follow what that might be.
The text was updated successfully, but these errors were encountered:
I'm not quite sure where the bug is though, so don't think I'll be able to push a PR.
BTW: why is this labeled "feature request"? It's an actual bug -- the code makes an assumption about how files are stored that's not true for all use cases.
Because ManifestFilesMixin was not around when collectfast was first built and support for it has never been implemented. Since integration with ManifestFilesMixin has never been supported there can't be bugs in the integration.
I'm using S3 with
ManifestFilesMixin
(it doesn't make sense to use S3 for staticfiles without it since invalidation becomes extremely complex and costly).:However,
collectfast
does not properly collect staticfiles. The manifest is missing, and no files are correctly copied onto the storage / bucket. There's no error though, and lots of processing is done for 2:45m.I'm guessing that
collectfast
makes some [wrong] assumptions regarding the underlying setup, but I can't quite follow what that might be.The text was updated successfully, but these errors were encountered: