fix(staging): point Social service URL to AWS Social via gqr-staging tunnel (18015)
Live root cause: dashboard gateway reached old developer FastAPI at social.sai-onchain.me and 404'd on the LinkedIn onboarding route. The gqr-staging reverse SSH tunnel now exposes AWS Social on host port 18015 (verified: healthz=200, POST route 422). - SOCIAL_BRANDING_SERVICE_URL: http://host.docker.internal:18015 (internal tunnel) - SOCIAL_BRANDING_PUBLIC_URL: https://social-staging.gqr.puter.wtf (public staging)
This commit is contained in:
@@ -16,8 +16,8 @@ services:
|
||||
user-service-staging:
|
||||
environment:
|
||||
DATABASE_URL: postgres://growqr:growqr@growqr-postgres:5432/growqr
|
||||
SOCIAL_BRANDING_SERVICE_URL: https://social.sai-onchain.me
|
||||
SOCIAL_BRANDING_PUBLIC_URL: https://social.sai-onchain.me
|
||||
SOCIAL_BRANDING_SERVICE_URL: http://host.docker.internal:18015
|
||||
SOCIAL_BRANDING_PUBLIC_URL: https://social-staging.gqr.puter.wtf
|
||||
PRODUCT_SERVICE_TIMEOUT_MS: 10000
|
||||
PRODUCT_INTERACTIVE_SERVICE_TIMEOUT_MS: 240000
|
||||
LLM_PROVIDER: opencode
|
||||
|
||||
Reference in New Issue
Block a user