本页面为机器翻译。阅读英文原文。

Component

core/ai-agent/dify-worker

The Dify task worker — the Celery consumer that runs everything a Dify installation does off the request path: indexing uploaded documents into the vector datastore, executing scheduled and queued workflow runs, generating dataset segments, and delivering mail and webhooks. It takes work from the Redis-compatible broker wired through the `cache` uses-socket, reads and writes the platform's relational model in the PostgreSQL backend wired through `backend`, and writes embeddings into the vector datastore wired through `vector_store`. Workflow code nodes it executes run in the sandbox wired through `sandbox`, and outbound requests to addresses a user supplied are routed through the forward proxy wired through `ssrf_proxy`. It serves no port and nothing connects to it — work reaches it through the broker — so it publishes no provides contract and renders as a stateless worker tier.

版本

1.0.01.1.0

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:7c4ad899822ecdbfd1a53335cb6937b11fd10217e1890ed1a4228178669035f8
发布时间
2026-11-10T10:07:55Z
签名身份
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

签名

  • 官方application/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:7938d27dd7a37a9d6706df74a66187a28fcf33a9f2abd1bb50b8c6faa3fec564

此版本的引用

oci://hub.aggrega.ai/component/core/ai-agent/dify-worker:1.0.0

开发者参数

开发者在 Aggregate 中设置的值。

名称类型默认值必需描述
vector_index_prefixstringVector_index否Name prefix the worker gives the collections it creates in the wired vector datastore. It matches the API server's prefix, because the two write the same collections.
indexing_max_segmentation_tokensinteger (min 1)4000否Longest segment, in tokens, the dataset indexer produces when it splits a document.

运维规格

运维人员按环境调整的基础设施规格。

名称类型默认值必需描述
engine_versionstring1.17.0否Dify API container image tag. The API server, the scheduler and this worker run the same image, so a Release moves all three together.
log_levelstring (DEBUG | INFO | WARNING | ERROR | CRITICAL)INFO否Log verbosity the worker emits.
concurrencyinteger (min 1)4否Number of task slots one worker process runs in parallel. Raising it raises throughput and the worker's memory ceiling together, so it is sized with compute.memory.
computeobject—否—
overridesobject (open)—否Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

输出契约

此组件通过 uses 拓扑向使用方发布的值。

未声明输出值。

uses 套接字

此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。

backend

选择器
component.aggrega.ai/category=datastore
注入
env

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
credentialfeature.aggrega.ai/kind=secret否env是Optional password the worker presents to the backend this connection reaches, shared with that backend. When attached, supplies the backend password via the credential subsystem; unattached, the Recipe uses the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password.

cache

选择器
component.aggrega.ai/category=datastore
注入
env

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
server_cafeature.aggrega.ai/kind=secret否file是Optional authority the worker checks the cache's certificate against while the cache publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and points the cache client and the task broker at the file. The build halts on a server_ca publishing no Secret name, and on one wired to a cache served without TLS. Fill it with core/referenced-secret.

vector_store

选择器
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
注入
env

此套接字未声明附加槽位,因此经由它的连接不携带任何附加项。

sandbox

选择器
component.aggrega.ai/category=ai-agent
注入
env

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
credentialfeature.aggrega.ai/kind=secret否env是Optional execution-key credential the worker presents on every request to the sandbox this connection reaches. The same credential is attached to the code_execution_key slot on the sandbox, so both ends hold the same value. Unattached, the Recipe uses the pinned development literal `dify-sandbox`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

plugin_daemon

选择器
component.aggrega.ai/category=ai-agent
注入
env

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
credentialfeature.aggrega.ai/kind=secret否env是Optional credential the worker presents on every call it makes to the plugin runtime this connection reaches. The runtime holds the same key in its plugin_daemon_key slot and the API server presents it on its own connection, so the credential is attached to all three or to none: attaching it to some of them leaves the rest carrying a different value, which renders cleanly and is refused when the call is made. Unattached, the Recipe uses the pinned development literal `dify-plugin-daemon-server-key`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

ssrf_proxy

选择器
component.aggrega.ai/category=ai-agent
注入
env

此套接字未声明附加槽位,因此经由它的连接不携带任何附加项。

附加槽位

Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。

槽位选择器必需注入敏感描述
secret_keyfeature.aggrega.ai/kind=secret是env是Required application-secret credential. The worker decrypts stored model-provider credentials under it, so it carries the same secret as the API server. There is no default: the build halts when nothing fills this slot.
inner_api_keyfeature.aggrega.ai/kind=secret否env是Optional credential the plugin runtime presents on every call back into the internal API, which the worker compares against its own. The worker and the API server declare this slot under the same name and the plugin runtime presents it on its connection to the API server, so the credential is attached to all three or to none: attaching it to some of them leaves the rest carrying a different value, which renders cleanly and is refused when the call is made. Unattached, the Recipe uses the pinned development literal `dify-plugin-inner-api-key`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

自注入允许列表

env

关系

与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。

使用

被使用

Component 概念参考 →

Aggrega 目录 — 收录组件、功能、配方以及渲染它们的插件的开放索引。

基于共享的 Aggrega 设计系统构建。

隐私