Repository navigation
First run: the console's Set up your server flow (F1) - #156
Merged
Merged
Conversation
capture-setup.mjs drives the --setup server: the account page, its hand-over, then the console's eight setup steps and the Overview's Finish setting up card, on a generated books folder whose tags and folder names disagree. capture-admin.mjs marks its servers set up so the flow never takes its shots.
The admin account still comes from the printed banner or --setup, whose page now asks only for the account and hands over. Each of the eight steps gets a section and a screenshot, plus the Overview's Finish setting up card; the quickstarts point their library step at the flow.
The /setup page asks only for the account (old library fields still accepted, marking the folder step done), the console flow and its Overview card in web-ui.md, GET/PUT /admin/setup and POST /admin/setup/preview in the reference, invalid_setup_step, the setup_state key and migration 0053, the settings.setup audit action, --setup in configuration.md, and the mapping row.
# Conflicts: # docs-developers/server/auth-and-security.md # docs-users/getting-started/first-run.md
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
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.
This documents first-run setup Phase F1 (KodeStar/audiosilo-server#162, merged): the console's "Set up your server" flow.
--setupare kept as the way the admin account is made, and--setupnow asks for the account only. The Docker, Unraid and binary install pages and the console tour now point at the flow.web-ui.md: the/setuphandover and a new "The first-run setup flow" section.configuration.md:--setupand how config-declared libraries show.GET/PUT /admin/setupandPOST /admin/setup/preview, plus thePOST /setupchanges and the error codes.data-model.md:setup_stateand migration 0053, plus the audit action.screenshots/capture-setup.mjsbuilds a books folder whose tags and folder names disagree.capture-admin.mjsmarks the demo servers as set up first, so the admin shots don't land on the flow.The docs build passes. The branch had
/simplifyand/code-review high --fix. The screenshots were captured before the review's refactor of the capture scripts, and the pipeline wasn't re-run after it (syntax-checked only).Pairs with KodeStar/audiosilo-server#162.