Skip to content

feat(deploy): DGX standalone compose (ai-server only, 24855) + confirmed-topology runbook - #72

Closed
dhkim-kr wants to merge 2 commits into
Masterfrom
deploy/backend-integration-surface
Closed

dhkim-kr wants to merge 2 commits into
Masterfrom
deploy/backend-integration-surface

Conversation

@dhkim-kr

@dhkim-kr dhkim-kr commented Jul 20, 2026

Copy link
Copy Markdown
Member

Why

#71 was merged at head e4bb0bb, moments before commit 5388210 (the DGX deployment file) reached the branch — same merge-window race as #70/#71. This PR carries that stranded commit plus a deployment-blocking .dockerignore fix found during the pre-deploy file audit. Base is Master; single merge; nothing else to merge first.

Commit File What
5388210 infra/deploy/docker-compose.dgx.yml (new) Standalone DGX compose (never combined with dev compose): ai-server only — no postgres/api (DB container :28881 already runs on the DGX, admin-managed), distinct project+container names (neuro-sync-ai-dgx/ns-ai-server-dgx), production CMD (no --reload, no source mounts), env_file .env with PROMPTS_BASE_DIR re-pinned to baked /app/prompts, extra_hosts host-gateway DB-hairpin fallback, restart: unless-stopped, port 24855:8001
5388210 docs/ai/deployment_integration_plan.md §3 Confirmed topology (one DGX Spark 223.194.33.26: DB :28881 running / ai-server :24855 to deploy) + 4-command runbook + backend base URL http://223.194.33.26:24855
1d8449e .dockerignore Build-blocker fix: the pre-existing docs exclusion removes the whole docs tree from the build context, so the Dockerfile's COPY docs/ai/prompts /app/prompts (added in #71) would fail the DGX image build — never caught locally because the dev workstation has no docker. Negations !docs/ai/prompts(/**) re-include only the prompts subtree. Also excludes _archive (42MB / 1,856 files) from the build context.

After merge — on the DGX (account that runs the DB container)

git clone https://github.com/Neuro-AI-Lab/neurosync.git && cd neurosync   # or git pull
# place apps/ai-server/.env (copied from dev workstation; never committed)
docker compose -f infra/deploy/docker-compose.dgx.yml up -d --build
curl -s localhost:24855/health

dhkim-kr added 2 commits July 20, 2026 16:26
…runbook with confirmed topology

- infra/deploy/docker-compose.dgx.yml: standalone (never an override) — no
  postgres/api services, distinct project/container names, env_file .env with
  PROMPTS_BASE_DIR re-pinned to baked /app/prompts, extra_hosts host-gateway
  fallback for DB hairpin, restart unless-stopped
- runbook §3: confirmed DGX topology (DB 28881 / ai-server 24855 on one host),
  4-command deploy, backend base URL http://223.194.33.26:24855
- refs docs/ai/deployment_integration_plan.md G1-G3
… COPY; exclude _archive from build context

- 'docs' exclusion predates the Dockerfile's COPY docs/ai/prompts (e4bb0bb) and
  would fail the DGX image build at that COPY step; negations re-include only
  the prompts subtree
- _archive (42MB, 1,856 files) no longer inflates the build context
- refs docs/ai/deployment_integration_plan.md §3
@dhkim-kr

Copy link
Copy Markdown
Member Author

Close — supersession map (filemanager, 8-PR 순차 머지 완료 후)

본 PR(#72, deploy/backend-integration-surface)의 산출물은 아래와 같이 Master에 이미 상위집합/현행화 형태로 랜딩되어 close합니다.

#72 산출물 상태 상위집합/현행화 근거
DGX standalone compose (infra/deploy/docker-compose.dgx.yml 등) 상위집합 #79(feat(api): F1~F3 연동 배선 + hospitals-map + DGX 배포 토폴로지)가 동일 compose 파일을 포함해 Master에 랜딩 (merge SHA 3ed0d3d)
배포문서 §3 (docs/ai/deployment_integration_plan.md 등) 현행화 #83(docs(ai): F1~F5 통합 문서 정리)이 배포 현황을 최신화해 Master에 랜딩 (merge SHA 1fa5599)
.dockerignore negation (!docs/ai/prompts, Dockerfile의 COPY docs/ai/prompts 성립 조건) 전제 소멸 — 이식 불요 ADR-041 T4가 #80(fix(ai-server): BUG-069~085 F1 자율대화...) 머지로 랜딩되며 apps/ai-server/DockerfileCOPY apps/ai-server/prompts /app/prompts로 이전, 빌드 경로가 docs/ai/prompts를 완전히 이탈함(merge SHA f6d7946). 현 Master .dockerignore에 이미 이 사유가 주석으로 명시되어 있어 손실 없이 close 가능

8개 PR(#77/#79/#80/#83/#78/#81/#82/#84) 순차 머지 완료. 이모지 없음.

@dhkim-kr dhkim-kr closed this Jul 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant