mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-10-04 14:39:42 +02:00
Codeman maintainer
2a32b5064a
Docker Compose deployment: Codeman runs in a container and spawns Docker cases as SIBLING containers through the mounted host socket (Docker-outside-of-Docker). Resolved the README conflict (master had grown to eight CLIs since the branch was cut) and moved the Compose blurb out of the feature bullets into Quick Start, next to the other ways of starting Codeman. Three review findings from the PR discussion are fixed here rather than left for a follow-up, because two of them are shipped-image problems: - `.dockerignore` excluded `.env` only at the ROOT. A pattern is matched against the whole context-relative path, so `docker/.env` — which the deployment's own README tells the user to fill with CODEMAN_PASSWORD and provider API keys — was picked up by `COPY . .` and baked into the image at /opt/codeman/docker/.env. Verified in both directions against a real build context: with a canary secret in docker/.env, the unfixed ignore file lets /ctx/docker/.env through, and `**/.env` (plus `**/.env.*` and a negation for the checked-in .env.example) leaves only the example behind. - `CODEMAN_CASES_PATH` moved the server's CASES_DIR but not the CLI's, which still hardcoded ~/codeman-cases, so `codeman skill install --case <name>` reported "Case not found" on exactly the deployment the override exists for. Both now resolve through config/cases-dir.ts. state-store.ts keeps its own literal on purpose: that one migrates the historical ~/claudeman-cases directory by name and is about the old default, not the active location. - CLAUDE.md gained the Compose paragraph (the sibling-container inversion, the three env vars, the .dockerignore and root-owned-bind traps) and .dockerignore joins the documented list of files that genuinely belong in the repo root. The PR's `mode === 'claude'` guard on dockerResumeId is an unrelated master bug fix riding along: appendResumeFlag() maps a resume id onto codex/gemini/pi/grok/ deepseek/omp/antigravity and RESUME_ID_SAFE accepts a UUID, so a Docker case's lastClaudeSessionId was handed to every non-claude CLI. Full gate green in a merge worktree: 6360 tests, lint, format, frontend syntax, public assets, lockfile.
38 lines
1.5 KiB
TypeScript
38 lines
1.5 KiB
TypeScript
/**
|
|
* @fileoverview Where case (project) folders live.
|
|
*
|
|
* Deliberately NOT instance-scoped, unlike `dataPath()`: `~/codeman-cases` is
|
|
* shared by every Codeman on the machine, the same way `~/codeman-users/<u>`
|
|
* user spaces are, so a beta instance sees the same projects as prod.
|
|
*
|
|
* `CODEMAN_CASES_PATH` overrides the location. Docker Compose deployments set
|
|
* it to a host-absolute bind mount so a Docker case's workspace resolves to the
|
|
* SAME absolute path inside Codeman and on the host daemon that mounts it.
|
|
*
|
|
* ⚠️ **One resolver, every caller.** This started life as three hardcoded
|
|
* `join(homedir(), 'codeman-cases')` copies. When only the web server's copy
|
|
* learned the override, `codeman skill install --case <name>` still looked in
|
|
* the home default and reported "Case not found" on exactly the deployment the
|
|
* override exists for. A new cases-dir consumer imports this; it does not
|
|
* rebuild the path.
|
|
*
|
|
* (`state-store.ts` keeps its own literal on purpose: that one migrates the
|
|
* historical `~/claudeman-cases` directory to `~/codeman-cases` by name, and is
|
|
* about the old default location rather than the active one.)
|
|
*
|
|
* @module config/cases-dir
|
|
*/
|
|
|
|
import { homedir } from 'node:os';
|
|
import { join } from 'node:path';
|
|
|
|
/** Absolute path to the shared cases directory. */
|
|
export function getCasesDir(): string {
|
|
return process.env.CODEMAN_CASES_PATH || join(homedir(), 'codeman-cases');
|
|
}
|
|
|
|
/** Absolute path to one case folder inside it. */
|
|
export function casePath(name: string): string {
|
|
return join(getCasesDir(), name);
|
|
}
|