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
When running the combination of frontend (on port 9000) and dotcom-rendering (on port 3030) together locally, it times out very frequently.
This happens most frequently when accessing PROD front paths like uk (http://localhost:9000/uk) via the dev-build Scala project
It also happens when running the facia Scala project directly, though I think this can improve the chances of getting a page to render this way.
It doesn't seem to time out when requesting PROD article paths like uk-news/2024/dec/05/uk-weather-storm-darragh-to-bring-80mph-gusts-as-amber-wind-warning-issued
I have tried increasing the timeout on the rendering configuration:
Problem summary
When running the combination of frontend (on port
9000
) and dotcom-rendering (on port3030
) together locally, it times out very frequently.This happens most frequently when accessing PROD front paths like
uk
(http://localhost:9000/uk
) via thedev-build
Scala projectIt also happens when running the
facia
Scala project directly, though I think this can improve the chances of getting a page to render this way.It doesn't seem to time out when requesting PROD article paths like
uk-news/2024/dec/05/uk-weather-storm-darragh-to-bring-80mph-gusts-as-amber-wind-warning-issued
I have tried increasing the timeout on the rendering configuration:
frontend/common/app/common/configuration.scala
Line 154 in 8b7f135
which can help but not always, and does slow down the feedback loop when developing
Workarounds
I sometimes use this workaround when needing to run DCR and frontend locally.
Tip
By using DCR as the base URL and adding the frontend URL into the path, it doesn't time out
http://localhost:3030/Front/http://localhost:9000/uk
The other alternative is to deploy to
CODE
, but this also takes time and delays developer feedback.The text was updated successfully, but these errors were encountered: