This repository was archived by the owner on Jul 13, 2026. It is now read-only.
Repository navigation
feat: one-click Coolify deploy via GitHub - #13
Merged
Merged
Conversation
…rgets Coolify (self-hosted OSS PaaS) becomes the one opinionated hosting target; GitHub stays the one repo layer. Since Coolify can only build from a git source, "Deploy to Coolify" pushes the project to a GitHub repo first (headless helper mirroring GitHubDeploymentDialog's Octokit sequence), then creates or redeploys a Coolify application pointed at that repo via its REST API, with opinionated defaults (first server, first project, nixpacks) so the click asks nothing. - New: coolify store/hook (instance URL + API token, mirroring useLinearConnection's manual-token pattern; no OAuth since Coolify is self-hosted and not in Nango's catalog), Settings > Integrations "Hosting" section, api.coolify-user (CORS proxy validation), api.coolify-deploy (create-or-redeploy + best-effort fqdn lookup), CoolifyDeploy.client, lib/github/pushToGitHub. - DeployButton drops Netlify/Vercel/GitLab/Cloudflare-placeholder entries; menu is now Deploy to Coolify + Push to GitHub. Old provider files are left in place for now; deleting them is a follow-up once Coolify is verified against a real instance. - Extracted the duplicated recursive project-file collection into deployUtils.collectProjectFiles (GitHubDeploy now uses it too). Verified: typecheck/lint/build pass; in the preview, the Hosting section renders, and a fake instance URL fails gracefully with a clear error through the full form -> hook -> proxy route path. Full deploy round-trip needs a real Coolify instance + token.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Phase 1 of the approved infra plan: Coolify (self-hosted OSS PaaS) becomes the single opinionated hosting target, GitHub stays the single repo layer.
pushFilesToGitHubRepohelper mirroring the existing dialog's Octokit sequence), then creates or redeploys a Coolify application pointed at that repo via its REST API. First deploy uses opinionated defaults (first server, first project, nixpacks buildpack, instant deploy) so the click asks nothing; the app UUID is remembered per chat for one-call redeploys.deployUtils.collectProjectFiles.Test plan
pnpm run typecheck/lint/buildpass🤖 Generated with Claude Code