-
Notifications
You must be signed in to change notification settings - Fork 62
Deploy to prod #8540
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
Deploy to prod #8540
Conversation
fix(deps): update dependency isomorphic-dompurify to v2.30.0
chore(api): rector to php80
…me-2.x chore(deps): update ghcr.io/browserless/chrome docker tag to v2.38.2
fix(deps): update dependency @sentry/node to v10.21.0
fix(deps): update dependency puppeteer-core to v24.26.0
chore(deps): update dependency rector/rector to v2.2.4
fix(deps): update dependency isomorphic-dompurify to v2.30.1
fix(deps): update dependency @pulumi/aws to v7.9.0
chore(deps): lock file maintenance
chore(deps): lock file maintenance
Disable ClassPropertyAssignToConstructorPromotionRector It only added string casts to lambda arguments.
Disable ClassPropertyAssignToConstructorPromotionRector It only added string casts to lambda arguments.
fix(deps): update dependency @pulumi/awsx to v3.0.1
chore(deps): lock file maintenance
fix(deps): update twig monorepo to v3.22.0
fix(deps): update dependency twig/extra-bundle to v3.22.1
chore(deps): update amazon/aws-cli docker tag to v2.31.33
chore(deps): update actions/checkout digest to 93cb6ef
chore(deps): update dependency @typescript-eslint/eslint-plugin to v8.46.4
chore(deps): update node.js to v24.11.1
reverse-proxy-nginx: disable dns cache for upstream
|
/fast-forward |
|
In this deployment, the domain was wrongly calculated as https://prod.ecamp3.ch. This led to the Kubernetes services not being reachable. When fixing the services to listen to the correct domain, various environment settings such as FRONTEND_URL, API_URL, CORS settings, allowed hosts in the API and so on were still incorrect. When correcting these manually as well, the Cloudflare cache kept on serving the erroneous version of environment.js. After correcting this as well, the services were back up and running. We should make sure to fix the calculation of the prod domain before deploying the next time. Unfortunately, staging didn't have this problem (because it uses the formulaic subdomain, unlike production). |
🏗️ Changes in this deployment
Includes the following non-renovate PRs:
Code to generate this overview
The above can be output locally using the following command: