feat(ai-autopilot): dokployTarget — second real DeployTarget adapter#162
Merged
Conversation
dokployTarget triggers a deployment of a pre-configured Dokploy application over
the Dokploy API (POST /api/application.deploy, x-api-key auth). Dokploy builds
and serves server-side, so it's a fetch-based target that takes no runner
session (unlike cloudflareTarget). Never throws: failures come back as
{ deployed: false, detail }. Creds from apiToken or DOKPLOY_AUTH_TOKEN/DOKPLOY_API_KEY.
Also fixes DEFAULT_DEPLOY_TARGETS spelling dockploy -> dokploy (real product name).
Closes #161
suleimansh
added
enhancement
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.
Closes #161. Follows the Cloudflare adapter (#159).
Adds the second deploy target Rom named. Unlike Cloudflare (a
wranglerCLI run in the session), Dokploy is API-driven, so this is afetch-basedDeployTarget.dokployTarget({ serverUrl, applicationId }):POST ${serverUrl}/api/application.deploywith anx-api-keyheader and{ applicationId, title, description }(verified against the Dokploy API docs).redeploy: trueusesapplication.redeploy.apiTokenorDOKPLOY_AUTH_TOKEN/DOKPLOY_API_KEY.{ deployed: false, detail }. Dokploy doesn't return the public URL from the trigger, so success reports the triggered deployment.Also fixes the
DEFAULT_DEPLOY_TARGETSspellingdockploy→dokploy(the real product name, matching its API +DOKPLOY_*env vars); tests updated.Verification: 8 unit tests with a fake fetch (endpoint + header + body, URL normalization, redeploy, missing-token/applicationId short-circuits, env-token fallback, non-2xx surfacing, network-rejection catch) — 257 tests green, typecheck+build clean, runtime export verified. Live deploy against a real Dokploy server is infra-gated. Minor changeset.