Repository navigation
feat(init): create the first admin without reading container logs #275
Description
Why
The quickstart's last step asks people to read docker compose logs -f api to find how to become the first admin. That is the moment a first-time user is most likely to give up.
What
seamless init(and the templates) end by printing a sign-in link or one clear next command for the owner- Works for the
--localpath and the interactive path - Docs quickstart updated to match
Done when
- A new user goes from
npx seamless-cli initto signed in as admin without opening logs, on a clean macOS machine and a clean Linux machine docs/start/firstAdmin.mdxno longer mentionsdocker compose logs- The templates'
docker:logsscript is not part of the first run instructions - Covered by a conformance spec once test(conformance): cover CLI commands, bearer transport, the dashboard and types PRs #209 runs
seamless init
Activity
feat(owner-code): print the owner's code so the first admin needs no …
docs(start): get the first admin's code from seamless owner-code
Bccorb commentedon Oct 21, 2026
Done.
seamless owner-code(#281) shipped in CLI 0.24.0, the first-admin docs were rewritten in fells-code/seamless-auth-docs#119, and the clean-machine runs on Linux x64, Linux arm64 and macOS reached an admin session without reading container logs (fells-code/seamless-auth-api#385, Phase 4 comment; script in #288).