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

[SERVER] Serve static assets from S3 and CloudFront #61

Closed
willroberts opened this issue Sep 27, 2022 · 0 comments · Fixed by #71
Closed

[SERVER] Serve static assets from S3 and CloudFront #61

willroberts opened this issue Sep 27, 2022 · 0 comments · Fixed by #71
Assignees
Labels
enhancement New feature or request infrastructure Related to infrastructure / deployments

Comments

@willroberts
Copy link
Collaborator

willroberts commented Sep 27, 2022

When loading the browser client in the development environment, all assets are served over Express in the API process.

This results in 75MB of additional data transfer to users: 47MB for duelyst.js, vendor.js, and duelyst.css, and 28MB for additional resources (music, images, and more).

We already have code for serving these from S3 for the production environment, so we should make sure this works and make use of it.

This will reduce both cloud provider costs and CPU utilization on the API process.

@willroberts willroberts added enhancement New feature or request infrastructure Related to infrastructure / deployments labels Sep 27, 2022
@willroberts willroberts self-assigned this Sep 27, 2022
@willroberts willroberts changed the title [SERVER] Serve static assets from S3 (and maybe CloudFront) [SERVER] Serve static assets from S3 and CloudFront Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request infrastructure Related to infrastructure / deployments
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant