You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 8, 2023. It is now read-only.
Currently the warmup configuration only supports a single url that is queried to warm up the service. It would be nice if this was a list and edward queried the urls in order. This would allow us to exercise the service from multiple endpoints.
For a web server, a single url might not be enough to warm up static resources (js, sass). Currently, these resources would only be compiled upon visiting the specific pages where we often have to wait around while the page loads. With multiple warmup urls, we could compile all resources before ever accessing the service.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the
warmup
configuration only supports a single url that is queried to warm up the service. It would be nice if this was a list andedward
queried the urls in order. This would allow us to exercise the service from multiple endpoints.For a web server, a single url might not be enough to warm up static resources (
js
,sass
). Currently, these resources would only be compiled upon visiting the specific pages where we often have to wait around while the page loads. With multiple warmup urls, we could compile all resources before ever accessing the service.The text was updated successfully, but these errors were encountered: