You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8409951
Browse filesBrowse the repository at this point in the historyBrowse files
fix(fork): VPS deploy skips docs-only commits and builds once per burst of merges
Closes#29. A range that changes only docs, Markdown, workflows, desktop,
mobile, marketing or test files moves the running checkout without a build.
A build starts only after main has not moved for 10 minutes. The busy-agent
check runs at most every 5 minutes and stops at the first busy project. The
service runs at low CPU, IO and process priority with MemoryHigh=6G.
Copy file name to clipboardExpand all lines: docs/fork.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,8 +136,10 @@ The client setting `forkChangelogEnabled` turns on a changelog of the fork. It i
136
136
137
137
The VPS server follows fork main. The timer `t3-deploy.timer` runs `scripts/fork-vps/deploy.sh` one minute after each run ends.
138
138
139
-
- When main has a new commit, the script builds it while the old server keeps running. It builds each commit once.
140
-
- It switches only when no agent turn runs. A server restart cancels running turns. T3 resumes them only when "Recover interrupted agents" or "Continue threads after restarts" is on. While agents run, the next run tries again.
139
+
- When the new commits change only paths that do not reach the server build, the script moves the running checkout to the new commit without a build or a restart. These paths are `docs`, `*.md`, `.github`, `apps/desktop`, `apps/mobile`, `apps/marketing` and test files.
140
+
- Otherwise it waits until main has not moved for 10 minutes, so a burst of merges gets one build. Then it builds main while the old server keeps running. It builds each commit once.
141
+
- It switches only when no agent turn runs. A server restart cancels running turns. T3 resumes them only when "Recover interrupted agents" or "Continue threads after restarts" is on. While agents run, it checks again after 5 minutes, because each check starts one node process per project.
142
+
-`t3-deploy.service` runs at a low CPU, IO and process priority. Above 6 GB of memory, the kernel slows the build instead of taking memory from the other apps on the VPS.
141
143
-`/opt/t3code` is a link to `/opt/t3code-a` or `/opt/t3code-b`. The script builds in the other folder, moves the link and restarts `t3-server`.
142
144
- If the new server does not answer, the script moves the link back.
0 commit comments