Publish the Chronicle Workbench port from cratis run - #55
Merged
Conversation
The Stage container bundles a Chronicle kernel that serves the Workbench on port 35000, but the run command only published the Stage API, so a play session could not be inspected. Publish 35000 as well, with a --workbench-port option for the host side, and print both URLs on startup.
Chronicle 16.11.0 replaces ChronicleConnectionString.DisableTls with SkipTlsValidation — the client now always connects over TLS and the option only relaxes certificate validation — so the connection, login and the documented connection-string option follow that rename.
einari
force-pushed
the
feat/publish-workbench-port
branch
from
July 30, 2026 12:47
7042d93 to
0c2c261
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added
cratis runnow publishes the Chronicle Workbench alongside the Stage API, so a play session's events, observers and read models can be inspected while it runs. The Workbench is athttps://localhost:35000— sign in with the Stage image's development credentials.--workbench-portoption oncratis runfor choosing the host port the Workbench is published on.Changed
cratis runprints both the Stage API and the Chronicle Workbench URL when a session starts.disableTlsconnection-string option is replaced byskipTlsValidation, following Chronicle 16.11.0. The client always connects over TLS; the option now only controls whether the server's certificate is validated, which is what lets the CLI trust a development server's self-signed certificate.