Mandu Deployment
SkillCloud & infraProduction deployment patterns for Mandu applications
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Mandu Deployment skill
What this skill tells your AI
The instructions your AI receives, as published by konamgil/mandu in docs/archive/skills/mcp-v0/mandu-deployment/SKILL.md and read by ahel’s review.
Mandu 앱을 프로덕션 환경에 안전하고 효율적으로 배포하기 위한 가이드입니다.
Agent Workflow Contract
This skill is a Domain addendum. It must not replace mandu-agent-workflow.
Use it only after mandu.agent.plan selects the deploy domain.
Canonical workflow step: plan -> apply -> verify.
Preferred MCP tools:
| Step | Tools |
|---|---|
| plan | mandu.agent.plan, mandu.deploy.plan |
| apply | mandu.agent.apply, mandu.deploy.compile |
| verify | mandu.agent.verify, mandu.deploy.preview |
| repair | mandu.agent.repair |
Allowed file edits:
.mandu/deploy.intent.json- Provider artifacts named in the plan, such as
render.yaml,Dockerfile,docker-compose.yml,fly.toml,vercel.json, ornetlify.toml - CI workflow files only when deploy automation is explicitly requested
Verification command:
mandu agent verify --changed --json --write
Common failures:
- Executing a provider deploy before a dry-run or preview step
- Writing secrets into tracked config
- Changing provider artifacts without route/deploy intent verification
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
핵심 원칙
- Bun 네이티브: Bun 런타임과 번들러를 최대한 활용
- 환경 분리: 개발/스테이징/프로덕션 환경 명확히 구분
- 자동화: CI/CD를 통한 일관된 배포 프로세스
- 보안 우선: 민감 정보는 환경 변수로 관리
Provider Artifact Examples
Use these examples only after mandu.agent.plan selects the deploy domain and
mandu.agent.apply has produced the intended action order.
Render 배포 (권장)
# render.yaml
services:
- type: web
name: mandu-app
runtime: node
buildCommand: bun install && bun run build
startCommand: bun run start
envVars:
- key: NODE_ENV
value: production
- key: BUN_ENV
value: production
Docker 배포
FROM oven/bun:1.3.14
WORKDIR /app
COPY package.json bun.lockb ./
RUN bun install --frozen-lockfile --production
COPY . .
RUN bun run build
EXPOSE 3000
CMD ["bun", "run", "start"]
배포 체크리스트
빌드 준비
-
bun run build성공 확인 - 번들 크기 최적화 (tree-shaking, code-splitting)
- 환경 변수 설정 완료
플랫폼 설정
- Render/Docker 설정 파일 작성
- 헬스체크 엔드포인트 구현
- 로깅 설정 완료
보안
- 민감 정보 환경 변수로 분리
- HTTPS 강제 적용
- 보안 헤더 설정
모니터링
- 에러 트래킹 설정
- 성능 모니터링 구성
- 알림 설정
규칙 카테고리
| Category | Description | Rules |
|---|---|---|
| Build | 프로덕션 빌드 최적화 | 2 |
| Platform | 플랫폼별 배포 설정 | 3 |
| Container | Docker 컨테이너화 | 2 |
| CI/CD | 자동화 파이프라인 | 1 |
→ 세부 규칙은 rules/ 폴더 참조
Signals
- GitHub stars
- 46
- Forks
- 3
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
mandu-deployment- Source
- github.com/konamgil/mandu