Repository navigation
Release v0.9.10 - #390
Merged
Merged
Release v0.9.10#390
Conversation
Matches Dokploy services to Capy projects (repo + repo-relative path + branch) and writes Dokploy deploy targets: discover -> plan file -> --dry-run (plan_id) -> --confirm, one keep PR per repo. Always JSON on stdout, never prompts. Pushes no values. - The Dokploy environment name outranks the default-branch rule when they name different Capy branches (a develop default branch deployed to a staging environment maps to staging, needs_review). - capy connect dokploy --discover no longer creates deploy targets. - The Dokploy base URL is the org system variable _CONNECTOR_DOKPLOY_BASE_URL. Only org admins save it; a missing URL is a structured refusal (unanswered: base_url, exit 3).
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
1 participant
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.
capy 0.9.10
New
capy deploy dokploy --discoversets up Dokploy deploys for a whole org. It matches each Dokploy service to a Capy project by its GitHub repo, its folder in the repo and its branch, then proposes a deploy target for each match, ratedcertainorneeds_review. It is built for agents: it always prints JSON and never prompts.--plan <file> --dry-runto get aplan_id, then--plan <file> --confirm <plan_id>to write the targets..capy/deploy.jsonthrough one pull request per repo, on the repo's default branch. No values are read, pushed or changed.capy help --jsonunderschemas.deploy_dokploy_plan.--base-urlonce saves it for everyone in the org. Only org admins can save it. When it is missing, the command stops withDOKPLOY_SETTINGS_MISSINGand says which flag to pass (exit code 3).Changed
capy connect dokploy --discoverno longer creates deploy targets. It only imports values. Usecapy deploy dokploy --discoverfor targets.