Skip to content
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

What is the best way for us to make sure static assets are compressed in azure #20

Closed
aaronhans opened this issue Dec 10, 2019 · 3 comments
Assignees
Labels
invalid This doesn't seem right
Milestone

Comments

@aaronhans
Copy link
Contributor

Could we check in with other teams or do our own research and come up with a deployment process we should follow that will make sure our static assets are compressed (gzipped or brotli'd) when delivered to end users.

We can put them in blog storage or pre compress as part of the build process and deliver directly from our server, I don't have an opinion on the best way to accomplish this, we can use whatever process is easiest in our azure environment

@carterm
Copy link
Contributor

carterm commented Dec 12, 2019

With our current Azure environment, all text content appears to have the encoding type "gzip." We may already be good to go here, but we should periodically check to make sure all our text content types are gzipped. Recommend close.

@ChadABratton
Copy link
Member

We can close this, Carter and Aaron confirmed this issue is no longer accurate.

@ChadABratton ChadABratton added the invalid This doesn't seem right label Dec 17, 2019
@ChadABratton ChadABratton added this to the Sprint 2 milestone Dec 17, 2019
@abquirarte
Copy link

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

4 participants