Full config reference for service.yaml - #578
Open
benitav wants to merge 20 commits into
Open
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
benitav
marked this pull request as draft
August 19, 2026 15:06
benitav
marked this pull request as ready for review
August 20, 2026 09:46
…rsync-docs into service-yaml-reference
This was referenced Aug 20, 2026
Closed
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.
Our drift agent pointed out a lot of undocumented config options for self-hosted instances, which inspired me to add a full reference (internal Slack ref).
Examples:
Main changes:
service.yamlreference, covering all user-facing config optionsdebug_api,block_local_jwks,use_legacyprobe, internal telemetry endpoint)Other:
AI usage: Claude Code did most of the actual work - checking what's available and writing the content - using my guidance. It referenced the
powersync-servicerepo for all available options and we then went through multiple review cycles (using the repo reviewer skills and my own manual review) to polish and improve readability. The Configuration Reference section would still benefit from a more technical review/once-over.