mark/vibn-agent-runner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(deploy): clarify correct push command for Coolify remotes; warn against subtree push

Browse Source
This commit is contained in:
mawkone
2026-06-10 21:44:06 -07:00
parent 82a41f7e95
commit cca2211b33
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ai-new-thread.md
View File

@@ -67,10 +67,16 @@ DO NOT treat `master-ai` as a single monorepo on Gitea. You must push changes in
**How deploys actually work:** `master-ai` is a single git repo. Each cloud app builds from its **own** Gitea
remote, from the matching subfolder. To ship a change, commit in `master-ai`, then
`git push <remote> HEAD:main` (e.g. `git push coolify_telemetry_gitea HEAD:main`), then trigger the
`git push <remote> HEAD:main` (e.g. `git push coolify_gitea HEAD:main` for vibn-frontend), then trigger the
Coolify deploy for that app (see `VIBNDEV.md`). `vibn-code` is a nested submodule with its own `.git` — commit &
push it via its own `origin`. Secret `.env*` files at the repo root are gitignored — never commit them.
**⚠️ IMPORTANT — never use `git subtree push` for these remotes.** Coolify is configured with
`vibn-frontend` as its **base directory**, so it expects the full `master-ai` repo at the remote root
and resolves the Dockerfile at `vibn-frontend/Dockerfile`. A subtree push flattens the repo to just the
subfolder contents, making the `vibn-frontend/` subdirectory disappear and breaking the build with
`open Dockerfile: no such file or directory`. Always use `git push <remote> HEAD:main [--force]`.
### Deploying the Telemetry Service manually via Coolify UI:
Because Coolify's API strictly blocks the programmatic creation of GitHub/Gitea Apps, the Telemetry service must be linked manually once:
1. Open [Coolify Dashboard -> vibn-infrastructure -> production](https://coolify.vibnai.com/project/f4owwggokksgw0ogo0844os0/environment/foskksoccksk0kc4g8sk88ok)