jaas-dashboard is the future of jaas.ai. For now, though, we'll just make it work by routing /static, /models and /controllers to the jaas-dashboard app.
You'll have to first make sure an image for jaas-dashboard is deployed to the Canonical docker hub at prod-comms.docker-registry.canonical.com/jaas.ai-dashboard.
Then:
./qa-deploy production sites/jaas.ai.yaml
watch microk8s.kubectl get all,ingress
And add jaas.ai to /etc/hosts:
echo "127.0.0.1 jaas.ai" | sudo tee -a /etc/hosts
^ once everything is Running and the ingress has ADDRESS 127.0.0.1 assigned, go to https://jaas.ai/models in a private window, and check dashboard works (although you'll have to accept the untrustworthy cert)
jaas-dashboard is the future of jaas.ai. For now, though, we'll just make it work by routing
/static,/modelsand/controllersto thejaas-dashboardapp.To do this, I've extended the
routes:blocks to support multiple paths per route, and in doing so I realised there are a bunch of possible optimisations that I think should be separately tackled in https://github.com/canonical-web-and-design/deployment-configs/issues/303.QA
You'll have to first make sure an image for
jaas-dashboardis deployed to the Canonical docker hub atprod-comms.docker-registry.canonical.com/jaas.ai-dashboard.Then:
And add
jaas.aito/etc/hosts:^ once everything is
Runningand the ingress hasADDRESS 127.0.0.1assigned, go to https://jaas.ai/models in a private window, and check dashboard works (although you'll have to accept the untrustworthy cert)Now clean up
/etc/hosts: