mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-02 21:58:11 +00:00
* 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>
221 lines
8.7 KiB
Plaintext
221 lines
8.7 KiB
Plaintext
---
|
|
title: Ferramenta de Raspagem de Sites Scrapfly
|
|
description: A `ScrapflyScrapeWebsiteTool` aproveita a API de web scraping da Scrapfly para extrair conteúdo de sites em diversos formatos.
|
|
icon: spider
|
|
mode: "wide"
|
|
---
|
|
|
|
# `ScrapflyScrapeWebsiteTool`
|
|
|
|
## Descrição
|
|
|
|
A `ScrapflyScrapeWebsiteTool` foi desenvolvida para aproveitar a API de web scraping da [Scrapfly](https://scrapfly.io/) para extrair conteúdo de sites. Esta ferramenta oferece recursos avançados de raspagem com suporte a navegador headless, proxies e recursos de bypass de anti-bot. Permite extrair dados de páginas web em vários formatos, incluindo HTML bruto, markdown e texto simples, sendo ideal para uma ampla variedade de tarefas de raspagem de sites.
|
|
|
|
## Instalação
|
|
|
|
Para utilizar esta ferramenta, é necessário instalar o Scrapfly SDK:
|
|
|
|
```shell
|
|
uv add scrapfly-sdk
|
|
```
|
|
|
|
Você também precisará obter uma chave de API da Scrapfly registrando-se em [scrapfly.io/register](https://www.scrapfly.io/register/).
|
|
|
|
## Passos para Começar
|
|
|
|
Para usar a `ScrapflyScrapeWebsiteTool` de forma eficaz, siga estas etapas:
|
|
|
|
1. **Instale as Dependências**: Instale o Scrapfly SDK usando o comando acima.
|
|
2. **Obtenha a Chave de API**: Cadastre-se na Scrapfly para obter sua chave de API.
|
|
3. **Inicialize a Ferramenta**: Crie uma instância da ferramenta com sua chave de API.
|
|
4. **Configure os Parâmetros de Raspagem**: Personalize os parâmetros de raspagem conforme suas necessidades.
|
|
|
|
## Exemplo
|
|
|
|
O exemplo a seguir demonstra como usar a `ScrapflyScrapeWebsiteTool` para extrair conteúdo de um site:
|
|
|
|
```python Code
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools import ScrapflyScrapeWebsiteTool
|
|
|
|
# Initialize the tool
|
|
scrape_tool = ScrapflyScrapeWebsiteTool(api_key="your_scrapfly_api_key")
|
|
|
|
# Define an agent that uses the tool
|
|
web_scraper_agent = Agent(
|
|
role="Web Scraper",
|
|
goal="Extract information from websites",
|
|
backstory="An expert in web scraping who can extract content from any website.",
|
|
tools=[scrape_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Example task to extract content from a website
|
|
scrape_task = Task(
|
|
description="Extract the main content from the product page at https://web-scraping.dev/products and summarize the available products.",
|
|
expected_output="A summary of the products available on the website.",
|
|
agent=web_scraper_agent,
|
|
)
|
|
|
|
# Create and run the crew
|
|
crew = Crew(agents=[web_scraper_agent], tasks=[scrape_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
Você também pode personalizar os parâmetros de raspagem:
|
|
|
|
```python Code
|
|
# Example with custom scraping parameters
|
|
web_scraper_agent = Agent(
|
|
role="Web Scraper",
|
|
goal="Extract information from websites with custom parameters",
|
|
backstory="An expert in web scraping who can extract content from any website.",
|
|
tools=[scrape_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# The agent will use the tool with parameters like:
|
|
# url="https://web-scraping.dev/products"
|
|
# scrape_format="markdown"
|
|
# ignore_scrape_failures=True
|
|
# scrape_config={
|
|
# "asp": True, # Bypass scraping blocking solutions, like Cloudflare
|
|
# "render_js": True, # Enable JavaScript rendering with a cloud headless browser
|
|
# "proxy_pool": "public_residential_pool", # Select a proxy pool
|
|
# "country": "us", # Select a proxy location
|
|
# "auto_scroll": True, # Auto scroll the page
|
|
# }
|
|
|
|
scrape_task = Task(
|
|
description="Extract the main content from the product page at https://web-scraping.dev/products using advanced scraping options including JavaScript rendering and proxy settings.",
|
|
expected_output="A detailed summary of the products with all available information.",
|
|
agent=web_scraper_agent,
|
|
)
|
|
```
|
|
|
|
## Parâmetros
|
|
|
|
A `ScrapflyScrapeWebsiteTool` aceita os seguintes parâmetros:
|
|
|
|
### Parâmetros de Inicialização
|
|
|
|
- **api_key**: Obrigatório. Sua chave de API da Scrapfly.
|
|
|
|
### Parâmetros de Execução
|
|
|
|
- **url**: Obrigatório. A URL do site a ser raspado.
|
|
- **scrape_format**: Opcional. O formato em que o conteúdo da página será extraído. As opções são "raw" (HTML), "markdown" ou "text". O padrão é "markdown".
|
|
- **scrape_config**: Opcional. Um dicionário contendo opções adicionais de configuração de raspagem da Scrapfly.
|
|
- **ignore_scrape_failures**: Opcional. Determina se as falhas de raspagem devem ser ignoradas. Se definido como `True`, a ferramenta irá retornar `None` ao invés de lançar uma exceção caso ocorra uma falha na raspagem.
|
|
|
|
## Opções de Configuração Scrapfly
|
|
|
|
O parâmetro `scrape_config` permite personalizar o comportamento da raspagem com as seguintes opções:
|
|
|
|
- **asp**: Ativa o bypass de proteção anti-scraping.
|
|
- **render_js**: Ativa a renderização de JavaScript com um navegador headless na nuvem.
|
|
- **proxy_pool**: Seleciona um pool de proxies (por exemplo, "public_residential_pool", "datacenter").
|
|
- **country**: Seleciona a localização do proxy (por exemplo, "us", "uk").
|
|
- **auto_scroll**: Rola automaticamente a página para carregar conteúdo lazy-loaded.
|
|
- **js**: Executa código JavaScript personalizado via o navegador headless.
|
|
|
|
Para uma lista completa de opções de configuração, consulte a [documentação da API Scrapfly](https://scrapfly.io/docs/scrape-api/getting-started).
|
|
|
|
## Uso
|
|
|
|
Ao usar a `ScrapflyScrapeWebsiteTool` com um agente, o agente deverá fornecer a URL do site a ser raspado e pode opcionalmente especificar o formato e opções adicionais de configuração:
|
|
|
|
```python Code
|
|
# Example of using the tool with an agent
|
|
web_scraper_agent = Agent(
|
|
role="Web Scraper",
|
|
goal="Extract information from websites",
|
|
backstory="An expert in web scraping who can extract content from any website.",
|
|
tools=[scrape_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Create a task for the agent
|
|
scrape_task = Task(
|
|
description="Extract the main content from example.com in markdown format.",
|
|
expected_output="The main content of example.com in markdown format.",
|
|
agent=web_scraper_agent,
|
|
)
|
|
|
|
# Run the task
|
|
crew = Crew(agents=[web_scraper_agent], tasks=[scrape_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
Para um uso mais avançado com configurações personalizadas:
|
|
|
|
```python Code
|
|
# Create a task with more specific instructions
|
|
advanced_scrape_task = Task(
|
|
description="""
|
|
Extract content from example.com with the following requirements:
|
|
- Convert the content to plain text format
|
|
- Enable JavaScript rendering
|
|
- Use a US-based proxy
|
|
- Handle any scraping failures gracefully
|
|
""",
|
|
expected_output="The extracted content from example.com",
|
|
agent=web_scraper_agent,
|
|
)
|
|
```
|
|
|
|
## Tratamento de Erros
|
|
|
|
Por padrão, a `ScrapflyScrapeWebsiteTool` irá lançar uma exceção se a raspagem falhar. Os agentes podem ser instruídos a tratar falhas de forma mais flexível especificando o parâmetro `ignore_scrape_failures`:
|
|
|
|
```python Code
|
|
# Create a task that instructs the agent to handle errors
|
|
error_handling_task = Task(
|
|
description="""
|
|
Extract content from a potentially problematic website and make sure to handle any
|
|
scraping failures gracefully by setting ignore_scrape_failures to True.
|
|
""",
|
|
expected_output="Either the extracted content or a graceful error message",
|
|
agent=web_scraper_agent,
|
|
)
|
|
```
|
|
|
|
## Detalhes de Implementação
|
|
|
|
A `ScrapflyScrapeWebsiteTool` utiliza o Scrapfly SDK para interagir com a API Scrapfly:
|
|
|
|
```python Code
|
|
class ScrapflyScrapeWebsiteTool(BaseTool):
|
|
name: str = "Scrapfly web scraping API tool"
|
|
description: str = (
|
|
"Scrape a webpage url using Scrapfly and return its content as markdown or text"
|
|
)
|
|
|
|
# Implementation details...
|
|
|
|
def _run(
|
|
self,
|
|
url: str,
|
|
scrape_format: str = "markdown",
|
|
scrape_config: Optional[Dict[str, Any]] = None,
|
|
ignore_scrape_failures: Optional[bool] = None,
|
|
):
|
|
from scrapfly import ScrapeApiResponse, ScrapeConfig
|
|
|
|
scrape_config = scrape_config if scrape_config is not None else {}
|
|
try:
|
|
response: ScrapeApiResponse = self.scrapfly.scrape(
|
|
ScrapeConfig(url, format=scrape_format, **scrape_config)
|
|
)
|
|
return response.scrape_result["content"]
|
|
except Exception as e:
|
|
if ignore_scrape_failures:
|
|
logger.error(f"Error fetching data from {url}, exception: {e}")
|
|
return None
|
|
else:
|
|
raise e
|
|
```
|
|
|
|
## Conclusão
|
|
|
|
A `ScrapflyScrapeWebsiteTool` oferece uma forma poderosa de extrair conteúdo de sites usando as avançadas capacidades de web scraping da Scrapfly. Com recursos como suporte a navegador headless, proxies e bypass de anti-bot, ela consegue lidar com sites complexos e extrair conteúdo em diversos formatos. Esta ferramenta é especialmente útil em tarefas de extração de dados, monitoramento de conteúdo e pesquisa, onde a raspagem confiável de sites é necessária. |