fix: remove hardcoded GW_URL from Dockerfile and staging manifest
Build and Deploy to Kubernetes / build-and-deploy (push) Successful in 4m15s

GW_URL/GwUrl env vars were baked into the Dockerfile (ENV) and the
staging K8s manifest, overriding appsettings.*.json at runtime.
This meant merging to production still used the staging CMS URL.

Now only ASPNETCORE_ENVIRONMENT is set in the manifest; the correct
GwUrl is read from appsettings.Staging.json or appsettings.Production.json
depending on the environment — as intended.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
masoodafar-web
2026-05-14 01:35:18 +03:30
parent 77a835311a
commit eef13d1471
2 changed files with 0 additions and 5 deletions
-4
View File
@@ -28,10 +28,6 @@ spec:
env:
- name: ASPNETCORE_ENVIRONMENT
value: "Staging"
- name: GW_URL
value: "https://cms.se.kbs1.ir"
- name: GwUrl
value: "https://cms.se.kbs1.ir"
resources:
requests:
memory: "256Mi"