mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-02 13:48:09 +00:00
93dafe2637
Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com>
100 lines
3.2 KiB
Plaintext
100 lines
3.2 KiB
Plaintext
---
|
|
title: "CrewAI 엔터프라이즈"
|
|
description: "AI 에이전트 워크플로우를 배포, 모니터링 및 확장하세요"
|
|
icon: "globe"
|
|
mode: "wide"
|
|
---
|
|
|
|
## 소개
|
|
|
|
CrewAI AMP(Agent Management Platform)는 프로덕션 환경에서 crew와 agent를 배포, 모니터링, 확장할 수 있는 플랫폼을 제공합니다.
|
|
|
|
<Frame>
|
|
<img
|
|
src="/images/enterprise/crewai-enterprise-dashboard.png"
|
|
alt="CrewAI AMP Dashboard"
|
|
/>
|
|
</Frame>
|
|
|
|
CrewAI AOP는 오픈 소스 프레임워크의 강력함에 프로덕션 배포, 협업, 확장성을 위한 기능을 더했습니다. crew를 관리형 인프라에 배포하고, 실행을 실시간으로 모니터링하세요.
|
|
|
|
## 주요 기능
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Crew Deployments" icon="rocket">
|
|
몇 번의 클릭만으로 관리형 인프라에 crew를 배포하세요
|
|
</Card>
|
|
<Card title="API Access" icon="code">
|
|
기존 시스템과의 통합을 위해 REST API를 통해 배포된 crew에 접근하세요
|
|
</Card>
|
|
<Card title="Observability" icon="chart-line">
|
|
상세한 실행 추적과 로그로 crew를 모니터링하세요
|
|
</Card>
|
|
<Card title="Tool Repository" icon="toolbox">
|
|
crew의 역량을 강화할 수 있도록 도구를 게시하고 설치하세요
|
|
</Card>
|
|
<Card title="Webhook Streaming" icon="webhook">
|
|
실시간 이벤트와 업데이트를 시스템으로 스트리밍하세요
|
|
</Card>
|
|
<Card title="Crew Studio" icon="paintbrush">
|
|
노코드/로코드 인터페이스로 crew를 생성 및 커스터마이즈하세요
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## 배포 옵션
|
|
|
|
<CardGroup cols={3}>
|
|
<Card title="GitHub 통합" icon="github">
|
|
코드 배포를 위해 GitHub 리포지토리에 직접 연결하세요
|
|
</Card>
|
|
<Card title="Crew Studio" icon="palette">
|
|
코드 없는 Crew Studio 인터페이스를 통해 생성된 crew를 배포하세요
|
|
</Card>
|
|
<Card title="CLI 배포" icon="terminal">
|
|
더 고급 배포 워크플로우를 위해 CrewAI CLI를 사용하세요
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## 시작하기
|
|
|
|
<Steps>
|
|
<Step title="계정 가입하기">
|
|
[app.crewai.com](https://app.crewai.com)에서 계정을 생성하세요
|
|
<Card title="가입하기" icon="user" href="https://app.crewai.com/signup">
|
|
가입하기
|
|
</Card>
|
|
</Step>
|
|
<Step title="첫 번째 crew 만들기">
|
|
코드 또는 Crew Studio를 사용하여 crew를 만드세요
|
|
<Card
|
|
title="Crew 만들기"
|
|
icon="paintbrush"
|
|
href="/ko/enterprise/guides/build-crew"
|
|
>
|
|
Crew 만들기
|
|
</Card>
|
|
</Step>
|
|
<Step title="crew 배포하기">
|
|
crew를 Enterprise 플랫폼에 배포하세요
|
|
<Card
|
|
title="Crew 배포"
|
|
icon="rocket"
|
|
href="/ko/enterprise/guides/deploy-to-amp"
|
|
>
|
|
Crew 배포
|
|
</Card>
|
|
</Step>
|
|
<Step title="crew에 접근하기">
|
|
생성된 API 엔드포인트를 통해 crew와 연동하세요
|
|
<Card
|
|
title="API 접근"
|
|
icon="code"
|
|
href="/ko/enterprise/guides/kickoff-crew"
|
|
>
|
|
Crew API 사용
|
|
</Card>
|
|
</Step>
|
|
</Steps>
|
|
|
|
자세한 안내를 원하시면 [배포 가이드](/ko/enterprise/guides/deploy-to-amp)를 확인하거나 아래 버튼을 클릭해 시작하세요.
|