Understand any codebase instantly. System intelligence for codebases, built for humans and AI.
TypeScript aiai-memoryclaude-codeclicode-analysiscode-mappingcode-memorycodebase-understandingcodexdeveloper-toolsllmopenclawpersistent-memoryprogram-analysissoftware-architecturesystem-intelligencesystem-mapping
fix: ensure compose file exists on start even when backend is already healthy
Tanner Kocher907ccd534a3e
diff --git a/ix-cli/src/cli/commands/docker.ts b/ix-cli/src/cli/commands/docker.tsindex 1446417f..a8b09d62 100644--- a/ix-cli/src/cli/commands/docker.ts+++ b/ix-cli/src/cli/commands/docker.ts@@ -88,6 +88,20 @@ export function registerDockerCommand(program: Command): void {.alias("up").description("Start the IX backend (ArangoDB + Memory Layer)").action(async () => {+ // Always ensure standalone compose file exists so stop/restart work from any directory+ if (!existsSync(LOCAL_COMPOSE)) {+ try {+ mkdirSync(COMPOSE_DIR, { recursive: true });+ execFileSync(+ "curl",+ ["-fsSL", `${GITHUB_RAW}/docker-compose.standalone.yml`, "-o", LOCAL_COMPOSE],+ { stdio: "ignore" }+ );+ } catch {+ // Non-critical — start can still work from repo dir+ }+ }+if (isHealthy()) {console.log("[ok] Backend is already running and healthy");console.log(" Memory Layer: http://localhost:8090");