Provide hooks to override manifest file storage in ManifestFilesMixin

[Ryan Lopopolo]

My use case is that I would like to run collectstatic and store static assets in S3. However, I would like to store staticfiles.json locally so I can bake it into my deployment artifact.

It seems the only way to do this right now is to create a custom mixin ​like this one and override read_manifest and save_manifest to use a custom storage.

It seems the current behavior can be retained by using a FileSystemStorage with location = settings.STATIC_ROOT (aka self). Can we add a manifest_storage as an overridable property?

[Tim Graham]

I'm not sure if I understand the suggestion, can you provide a patch? Will it be backwards compatible?

[Ryan Lopopolo]

My intent is to add a layer of indirection to allow the manifest file to be saved to a separate storage backend than the static files themselves.

I've attached a patch. It should be backwards compatible.

[Ryan Lopopolo]

manifest_storage indirection

[Ryan Lopopolo]

The latest patch passes all tests when running

../venv/bin/python ./runtests.py staticfiles_tests.test_storage

I could not get the whole staticfiles suite to run

EDIT: I was doing something stupid. The entire suite passes on the master and stable/1.10.x branches.

[Tim Graham]

It might be fine, I've not done much work with that code to say if there might be a better design. Anyway, at least docs and tests are also needed.

[Carlton Gibson]

I'm going to close this as a duplicate of #27590 — both tickets are asking to allow configuration of where to store the manifest.

[Mariusz Felisiak]

Duplicate of #27590.