Repository navigation
Conversation
…ontract wording Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying paddock with
|
| Latest commit: |
cd96296
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8d05dc6d.paddock-7u2.pages.dev |
| Branch Preview URL: | https://g-docs-2.paddock-7u2.pages.dev |
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.
Docs: "Running as a service" and "Updating" in the shared CLI-contract wording (G2)
Both pages now follow the wording all six tools share (cli-contract SPEC 0.2), with the slugs and sidebar labels unchanged (
guides/running-as-a-service— "Keeping Paddock running on your laptop";guides/updating— "Updating Paddock"); only the page titles changed, to "Running as a service" and "Updating".Running as a service — reorganised into: intro (LaunchAgent / systemd user service, Windows not yet) · Installing (options table, waits until it answers, re-running is safe and keeps the unit's settings,
--dry-run, the npx / checkout +--from-checkout/ port refusals, linger and "never runs sudo") · Where things are (the unit runs this Node andcli.jsby real path; a removed Node →status/doctorwarn, reinstall fixes) · The commands (stop doesn't disable; uninstall keeps data and logs; logs 50 /-f/-n;startrunsreset-failed;--jsonon the actions) · Busy (new): stop/restart refuse with 75,--force→Overriding:,uninstalldoesn't ask,paddock busy0/75/3 · Logs (one file, rotated by copy-and-truncate at 8 MB × 3) · Exit codes (new) · the existing at-login/npx/access/known-unverified/Windows/server sections kept · link to Updating.Updating — the sequence sentence · options table · busy (75 before anything stops) · the 30 s / 20 lines / exit 6 / exit 7 wording · without a service (a foreground
servethat answers → asks you to stop it, exit 3) · the exit-5 table including the not-writablesudorow andPADDOCK_UPDATE_HINT· Docker and Watchtower (short, linking Deploying's full Compose block) · no automatic checks · run it from a terminal · exit codes now include 1 and 3 ·doctor· step by step · by hand.Docs-only, so no changeset (CONTRIBUTING). Built locally (
cd website && npm ci && npm run build), every new in-page anchor checked in the output (#checking-an-install-paddock-doctor,#linux-linger,#exit-codes, Deploying's#keeping-it-current), and both pages looked at in a browser (light theme, full page): headings, tables, the caution asides and code blocks all render.🤖 Generated with Claude Code