Open durack1 opened 4 months ago
Thanks for the catch. I should be able to fix on aims2 if hardcoded. But the link should not be hardcoded and we should have an issue to create a setting (env) for this...
Looping in @downiec
./components/NavBar/index.tsx: href="https://www.esgf.io/nodes.html"
@sashakames was there an intention of renaming the nodes aims2 -> esgf-node? If yes, that would be ideal, so we have that same template around the place esgf-node.someplace.somewhere
Yeah, essentially that will be the effect once we migrate the production Metagrid environment to Nimbus. esgf-node
will be backed by Kubernetes. aims2
may hand around for pre-release, but we will be clear that its the case and suggest users go to production.
I updated aims2.llnl.gov with the correct link. Will keep issue open until the update is merged into the next release.
Describe the bug
The "Federated Node" link in the current https://aims2.llnl.gov/ page links to https://www.esgf.io/nodes.html.![Screenshot 2024-04-09 at 3 27 29 PM](https://github.com/esgf2-us/metagrid/assets/3229632/7100cbc8-ba84-44dd-9b49-1f053531a20e)
This link doesn't resolve