With the new environment, files that used django swift
storage in the database were not accessible since the
environment changed.
This changes the view to get it from the swift container
like it should have this whole time.
I also removed the bit where it saves the file in the
record, because we never should have been doing that.
I had TODOs to remove it that I never got around to.
With the new environment, files that used django swift
storage in the database were not accessible since the
user changed.
Instead of trying to get hte file from the defunct storage,
this gets it from the swift container like it should have
this whole time.
I also removed hte bit where it saves the file in the
record, because we never should have been doing that.
I had TODOs to remove it that I never got around to.
Merge #380417 from ~codersquid/hexr:production-swift-container-usage
Remove swift container api call
Production has rw permissions to the two containers
we use, but it does not have permissions to create
new containers. This change removes hte call to check/create
containers.
That means that if anyone ever deploys a completely
new environment that the containers need to exist. They
can be created using the swift command line tool with
the credentials of the tenant.
Merge #380482 from ~codersquid/hexr:change-readme-comments
update README with current info
The sphinx docs are not maintained. This adds
a link to the google docs folder for developers
and a link to the mojo spec that deploys staging
and production
