Staging builds get garbage collected after 24hrs so I had to re-run the pipeline to get a new image built. It's up now.
Try again, kustomize was injecting labels that caused traffic to route to unintended services:
I can get you logs access via the ArgoCD dashboard, I just need to setup the SSO roles for it. As for the rest of this: write better code/skill issue
This is being worked. Goal was to get the site online and work those deployment bugs before getting the automation stood up.
@Quaternions nope the docs for API_HOST called for a trailing slash which was not appropriate. The code is fine.
Not quite, I pushed an update to trim the /api prefix and now we're all set. Thanks!
I guess to be clear, the middleware change is non-functional and I posted the URL so that @interpreterK can see.
So you either found the URL in:
- The issue in this repo talking about how the website is not working
- The discord where the very next sentence say it is not functioning.
Then you opened…
New code is deployed at: https://maps.staging.strafes.net
Looks like the request to https://maps.staging.strafes.net/api/submissions?Page=1&Limit=100 is a 404 however.