I remember that Cylc used to provide a very useful web interface for browsing workflow logs. I think this used to be Cylc Review. Am I right that the modern replacement is Cylc Hub? The documentation on this part is a bit thin, so I want to check whether I’m looking in the right place.
When I run cylc hub, it starts up and prints a local URL. Opening that URL in a browser shows a sign‑in page asking for a username and password. However, my system username and password don’t work, and I’m not sure where the authentication for Cylc Hub is configured.
Could someone point me to the correct configuration for enabling login, or explain what the expected authentication mechanism is? And more generally, what’s the recommended way to get the “workflow logs website” up and running in current Cylc versions?
Cylc Hub is just Jupyter Hub, configured for Cylc use, extensive documentation can be found here.
Jupyter Hub is something that has to be deployed by system administrators as it requires raised privileges to function.
By default, Jupyter Hub is configured to use system authentication, so should work with your regular username/password. However, in order for this to work, you must list the user accounts you wish to grant access, to enable all accounts, add this configuration:
The web interface you remember is indeed Cylc Review. This isn’t available at the time of writing as we have just finished porting it to Cylc Hub, but haven’t released it yet.
Keep an eye on the 8.6 release thread, we’ll announce the release of cylc-uiserver 1.9.0 shortly which will include setup instructions for running Cylc Review behind Jupyter Hub.
For multi-user setups, Cylc Hub must be installed with the required permissions, however, for evaluation, we’ll be able to run Cylc Review standalone for single-user applications.
The new version of Cylc Review continues to provide the capability to provide a “public” web app that does not require login.
Thanks for the clarification. I’ll keep an eye on the release announcements for cylc‑uiserver 1.9.0. Cylc Review is an important feature for us, so I’m looking forward to the updated version.
The login works now after adding the configuration you suggested.
I’m running Cylc Hub without admin privileges, just to evaluate the current functionality and to be prepared once Cylc Review becomes available. After logging in, I see the Hub interface with items like My Server, Stop My Server, Logout, Cylc, Home, and Token. However, clicking on Cylc or My Server results in:
500 : Internal Server Error
Redirect loop detected.
If I stop and restart the server from the interface, I briefly see:
Your server is starting up.
You will be redirected automatically when it’s ready for you.
100% Complete
Server ready at /user/MY_USERNAME/
but this is immediately replaced by the same redirect‑loop error. The path /user/MY_USERNAME/ does not exist on my system.
Is this expected for a non‑privileged single‑user setup, or is there a minimal configuration I should add to avoid the redirect loop?