mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-04 06:29:22 +00:00
a237ebabba
* feat: adopt directory-based docs versioning with Edge channel 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> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
103 lines
3.2 KiB
Plaintext
103 lines
3.2 KiB
Plaintext
---
|
|
title: "CrewAI AMP"
|
|
description: "Implemente, monitore e escale seus fluxos de trabalho de agentes de IA"
|
|
icon: "globe"
|
|
mode: "wide"
|
|
---
|
|
|
|
## Introdução
|
|
|
|
CrewAI AMP(Agent Management Platform) fornece uma plataforma para implementar, monitorar e escalar seus crews e agentes em um ambiente de produção.
|
|
|
|
<Frame>
|
|
<img
|
|
src="/images/enterprise/crewai-enterprise-dashboard.png"
|
|
alt="CrewAI AMP Dashboard"
|
|
/>
|
|
</Frame>
|
|
|
|
CrewAI AMP expande o poder do framework open-source com funcionalidades projetadas para implantações em produção, colaboração e escalabilidade. Implemente seus crews em uma infraestrutura gerenciada e monitore sua execução em tempo real.
|
|
|
|
## Principais Funcionalidades
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Implantação de Crews" icon="rocket">
|
|
Implemente seus crews em uma infraestrutura gerenciada com apenas alguns
|
|
cliques
|
|
</Card>
|
|
<Card title="Acesso via API" icon="code">
|
|
Acesse seus crews implantados via REST API para integração com sistemas
|
|
existentes
|
|
</Card>
|
|
<Card title="Observabilidade" icon="chart-line">
|
|
Monitore seus crews com rastreamentos de execução e logs detalhados
|
|
</Card>
|
|
<Card title="Repositório de Ferramentas" icon="toolbox">
|
|
Publique e instale ferramentas para aprimorar as capacidades de seus crews
|
|
</Card>
|
|
<Card title="Transmissão via Webhook" icon="webhook">
|
|
Transmita eventos e atualizações em tempo real para seus sistemas
|
|
</Card>
|
|
<Card title="Crew Studio" icon="paintbrush">
|
|
Crie e personalize crews utilizando uma interface no-code/low-code
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## Opções de Implantação
|
|
|
|
<CardGroup cols={3}>
|
|
<Card title="Integração com GitHub" icon="github">
|
|
Conecte-se diretamente aos seus repositórios do GitHub para implementar
|
|
código
|
|
</Card>
|
|
<Card title="Crew Studio" icon="palette">
|
|
Implemente crews criados pela interface no-code do Crew Studio
|
|
</Card>
|
|
<Card title="Implantação via CLI" icon="terminal">
|
|
Use o CrewAI CLI para fluxos de trabalho de implantação mais avançados
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## Primeiros Passos
|
|
|
|
<Steps>
|
|
<Step title="Cadastre-se para uma conta">
|
|
Crie sua conta em [app.crewai.com](https://app.crewai.com)
|
|
<Card title="Cadastre-se" icon="user" href="https://app.crewai.com/signup">
|
|
Cadastre-se
|
|
</Card>
|
|
</Step>
|
|
<Step title="Construa seu primeiro crew">
|
|
Utilize código ou o Crew Studio para construir seu crew
|
|
<Card
|
|
title="Construir Crew"
|
|
icon="paintbrush"
|
|
href="/pt-BR/enterprise/guides/build-crew"
|
|
>
|
|
Construir Crew
|
|
</Card>
|
|
</Step>
|
|
<Step title="Implemente seu crew">
|
|
Implemente seu crew na plataforma Enterprise
|
|
<Card
|
|
title="Implantar Crew"
|
|
icon="rocket"
|
|
href="/pt-BR/enterprise/guides/deploy-to-amp"
|
|
>
|
|
Implantar Crew
|
|
</Card>
|
|
</Step>
|
|
<Step title="Acesse seu crew">
|
|
Integre-se ao seu crew através dos endpoints de API gerados
|
|
<Card
|
|
title="Acesso via API"
|
|
icon="code"
|
|
href="/pt-BR/enterprise/guides/kickoff-crew"
|
|
>
|
|
Usar a API do Crew
|
|
</Card>
|
|
</Step>
|
|
</Steps>
|
|
|
|
Para instruções detalhadas, consulte nosso [guia de implantação](/pt-BR/enterprise/guides/deploy-to-amp) ou clique no botão abaixo para começar.
|