Skip to content
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

DEVOPSs1412 : Europa on Next #135

Merged
merged 3 commits into from
Dec 20, 2023
Merged

DEVOPSs1412 : Europa on Next #135

merged 3 commits into from
Dec 20, 2023

Conversation

jsfillman
Copy link
Contributor

@jsfillman jsfillman commented Dec 19, 2023

After exhaustive troubleshooting, I found the root cause behind the 404 errors on the next cluster:

The next environment wasn't defined in Europa's env configs!

I've updated the relevant files to include, and thus build code for, a next env, which now shows up under /deploy/next.
I've gone ahead and tested this in the next cluster using image ghcr.io/kbase/ui:br-DEVOPS-1412-next.

@jsfillman jsfillman self-assigned this Dec 19, 2023
Copy link
Collaborator

@dakotablair dakotablair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Comment on lines +27 to +32
"next": {
"domain": "next.kbase.us",
"legacy": "legacy.next.kbase.us",
"public_url": "/"
},

Copy link
Collaborator

@dakotablair dakotablair Dec 19, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only place that was required to be updated to prevent the 404s that you ran into. It is the situation "using a deployed build with an undefined environment" which usually does not happen during development since the defaults from the .env file are used. We might want to update scripts/build_deploy.sh to use defaults from .env.

@jsfillman jsfillman merged commit 51b5db4 into main Dec 20, 2023
5 checks passed
@jsfillman jsfillman deleted the DEVOPS-1412-next branch December 20, 2023 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants