Transcripts

The guides show the short version of each journey. These pages are the long version: every command that was run against a real stack and every byte that came back, with nothing reconstructed from what the code looks like it should do.

There are three groups, and one page on the first start.

• Request paths: what a client or a browser sends to the protocol endpoints. Start here for sign-in, tokens, sessions, logout and the refusals.
• Admin paths: the admin API, one route at a time.
• Console paths: the routes the admin console uses to sign an administrator in and to forward calls to the admin API.
• First start: the Compose stack and odudu init, with every refusal.

A page is long on purpose, because it is a record rather than an explanation. If you want the explanation, read the guide that links to it. If you are changing Odudu and want to know how a transcript is made and kept true, read How the transcripts are captured and checked.