I have begun to experiment with Agola using a microk8s deployed cluster based on the example/kubernetes/simple yml resources.
For my use case I wish to initiate user direct runs using a locally cloned repo. I discovered while experimenting with the platform that creating accounts seemed to be limited to only working when a remote repo was available so I did a go build to get an agola cmd line binary and ran the following commands to create what I believe is an unlinked account.
export AGOLA_IP=`kubectl get service agola -o json | jq -r .spec.clusterIP` export AGOLA_PORT=`kubectl get service agola -o json | jq -r ".spec.ports.port"` ./agola user create -n karl -u http://$AGOLA_IP:$AGOLA_PORT ./agola.exe user token create -n karl -u http://$AGOLA_IP:$AGOLA_PORT -d --token "admintoken" -t default
However after doing this it became apparent that I cannot login to the web UI as I have no remotes configured.
The functionality hints that the presence of a real remote might not be needed if I used only userdirect runs, however I don’t appear to be able to use the web UI in that case to view any pipeline results if I was to use agola in a headless manner.
So my question is, can I use the full functionality of the agola UI without a remote ?