From cca2211b339d0dde9592e4e0c325058847fd70c1 Mon Sep 17 00:00:00 2001 From: mawkone Date: Wed, 10 Jun 2026 21:44:06 -0700 Subject: [PATCH] docs(deploy): clarify correct push command for Coolify remotes; warn against subtree push --- ai-new-thread.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ai-new-thread.md b/ai-new-thread.md index 9a48812f..afd60586 100644 --- a/ai-new-thread.md +++ b/ai-new-thread.md @@ -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 HEAD:main` (e.g. `git push coolify_telemetry_gitea HEAD:main`), then trigger the +`git push 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 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)