-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serve Whitehall's Number 10 assets from Asset Manager #268
Comments
@andrewgarner has just run I suspect these jobs might need to wait until the uploads in #404 have finished. |
I've asked 2ndline to compare the number of these assets on the filesystem to the number that have been created in the Asset Manager database. |
@h-lame ran the following commands in production to compare the assets on the filesystem to those in the Asset Manager database:
The number of assets in the database matches the number on the filesystem so we're all good to open a PR to update the nginx config to serve these assets from asset-manager. |
See alphagov/asset-manager#268 for more information. We [uploaded all historical number10 assets on 19 Jan 2018][1]. [1]: alphagov/asset-manager#268 (comment)
I've opened alphagov/govuk-puppet#7130 to update the nginx config to start serving these assets from Asset Manager. |
See alphagov/asset-manager#268 for more information. We [uploaded all historical number10 assets on 19 Jan 2018][1]. [1]: alphagov/asset-manager#268 (comment)
For reference, I requested the example asset in the description to confirm that it's being served by Whitehall in production:
|
I've tested the effect of this PR in integration and used Kibana to confirm that these assets are now being served by Asset Manager. Note. We don't currently have a realistic set of assets or asset-manager data in integration so I've had to create a Whitehall asset to mirror the example asset in the description.
|
These assets are now being served in production. I made the following request
And can see in Kibana that the request was eventually served by asset manager: |
I've moved the task to delete these assets to #405 so that we can close this issue. |
Now we are serving these assets from Asset Manager[1] they can be removed from the file system. This rake task can be run on the various environments to remove the files. [1] alphagov/asset-manager#268
Now we are serving these assets from Asset Manager[1] they can be removed from the file system. This rake task can be run on the various environments to remove the files. [1] alphagov/asset-manager#268
The Number 10 assets are currently served by the
PublicUploadsController
in Whitehall.These are used by the virtual tour on the History of 10 Downing Street page. There appears to be an XML file for each "tour" and these contain links to the assets in the /uploaded/number10 directory on assets.publishing.service.gov.uk (e.g. image_001.xml.erb).
Example number10 asset: https://assets.publishing.service.gov.uk/government/uploads/uploaded/number10/image_001.tiles/preview.jpg
Tasks
asset_manager:migrate_assets[uploaded/number10]
on productionThe text was updated successfully, but these errors were encountered: