이 페이지는 기계 번역되었습니다. 영어 원문 읽기.

Component

core/ai-agent/dify

The Dify API and console server — the control plane of a self-hosted Dify installation. It serves the console API the browser front end calls, the published application API, and the file endpoints, and it owns the platform's relational model: workspaces, applications, workflow definitions, datasets and the encrypted model-provider credentials. It stores that model in a PostgreSQL backend wired through the `backend` uses-socket, keeps sessions and the Celery task queue in a Redis-compatible cache wired through `cache`, and reads and writes dataset embeddings in a vector datastore wired through `vector_store`. Three sibling services complete the platform and reach it through their own sockets: code nodes execute in the sandbox wired through `sandbox`, model and tool plugins run in the plugin runtime wired through `plugin_daemon`, and outbound requests to addresses a user supplied are routed through the forward proxy wired through `ssrf_proxy`, so a workflow cannot reach a private address directly. Holds no durable state of its own — the backend, the cache and the vector datastore are the systems of record — so it renders as a stateless server. Exports its host, port and protocol to consumers via the uses topology. An application written in Dify's own export format, set as app_definition, is imported into the installation at deploy under the owner account the operator names. By default the server sends nothing to Dify's vendor: infra.telemetry_enabled turns on its usage events, update check, remote template lists and Creators Platform, and infra.marketplace_enabled its plugin marketplace, which model-provider plugins such as OpenAI's install from.

버전

1.0.01.1.0

출처

공식이 카탈로그가 공식 게시자로 인정하는 서명 ID로 서명되었습니다.
콘텐츠 다이제스트
sha256:6cde03e895a584a1d3af008e8015aa0aefb7e52eeb6f0005dc8ccfb09107b706
게시일
2026-11-15T08:08:52Z
서명 ID
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:ac95749c5717fc491f3efac7000fb5818ddd70e0247456c9885278be4e77d06d

이 버전의 참조

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

개발자 매개변수

개발자가 Aggregate에서 설정하는 값입니다.

BaseComponents#/schemas/BaseAgentParameter 확장

이름타입기본값필수설명
vector_index_prefixstringVector_index아니요Name prefix the platform gives the collections it creates in the wired vector datastore. Two installations sharing one datastore keep their collections apart by carrying different prefixes.
top_k_maxinteger (min 1)10아니요Highest retrieval top-k an application in this installation may request.
max_parallel_limitinteger (min 1)10아니요Highest parallel-branch count a workflow in this installation may run.
max_iterationsinteger (min 1)99아니요Highest iteration count an iteration node in this installation may run.
max_toolsinteger (min 1)10아니요Highest number of tools an agent in this installation may be given.
indexing_max_segmentation_tokensinteger (min 1)4000아니요Longest segment, in tokens, the dataset indexer produces when it splits a document.
app_definitionstring—아니요An application in Dify's own DSL, the YAML Dify exports for an application, carried verbatim. Realized by the helm and compose targets: when set, a one-shot step imports it once the installation is deployed. The step performs Dify's first-time setup if it has not run, creating the owner account named by infra.owner_email with the password attached to the owner_password slot; signs in as that account; leaves an application already present under the definition's app.name as it is; and otherwise imports the definition through Dify's console import, confirming the import when Dify holds it for confirmation, as it does for a DSL version newer than the installation's. When set, infra.owner_email and the owner_password slot are required and the build halts without them. When unset, nothing is imported and no step is rendered. An Aggregate's text is evaluated as a template before it is read, so a definition carrying Dify's own {{#...#}} variable references halts the build when written into an Aggregate as it stands; supply it as a parameter the Release fills, written into this value through toJson, and it arrives as written.

운영자 사이징

운영자가 환경별로 조정하는 인프라 사이징입니다.

이름타입기본값필수설명
portinteger (min 1024, max 65535)5001아니요Console-API and application-API listen port consumers connect to.
published_portinteger (min 1024, max 65535)—아니요Port published on the host's loopback address, 127.0.0.1, on Docker Compose, forwarding to infra.port inside the container; any process on this machine can reach it there. Unset, nothing is published. Kubernetes realizations refuse it; reach the Service with kubectl port-forward, or attach core/public-ingress.
engine_versionstring1.17.0아니요Dify API container image tag. The worker, the scheduler and this server run the same image, so a Release moves all three together.
log_levelstring (DEBUG | INFO | WARNING | ERROR | CRITICAL)INFO아니요Log verbosity the server emits.
external_base_urlstring아니요Externally reachable base URL of the installation, as a browser and an API client see it — the address the ingress tier publishes. The server composes the console, application, service-API and file URLs from it, which is what makes shared links and emailed links resolve. Left empty, the server derives each URL from the incoming request, which suits an installation reached only in-cluster.
console_urlstring—아니요Address a browser opens the console (core/ai-agent/dify-web) at, as scheme, host and port, for example http://127.0.0.1:3001. The server admits credentialed browser requests to its console API from this origin alone, so the console's sign-in works there, and composes the console links it hands out, such as the redirect after an OAuth sign-in, from it. A trailing / is dropped, and an address carrying any other path halts the build, since a browser sends an origin without one. Where infra.external_base_url is set too, this key decides the console's address and that one the other URLs. Unset, the console's address comes from infra.external_base_url where that is set, and otherwise is the image's own default, http://127.0.0.1:3000.
owner_emailstring—아니요Email address of the installation's owner account, read only when values.app_definition is set. The step that imports the application creates this account when it performs Dify's first-time setup, and signs in as it; on an installation whose setup has already run, it names an existing account allowed to import applications, and the password attached to the owner_password slot is that account's. Required when values.app_definition is set: the build halts when it is empty. It has no default.
telemetry_enabledbooleanfalse아니요Lets the server reach Dify's vendor for its anonymous usage events (otel.dify.ai, falling back to otel.dify.cn, when first-time setup runs), the update check the console makes (updates.dify.ai), the remote application and knowledge-pipeline template lists (tmpl.dify.ai) and publishing an application to the Creators Platform (creators.dify.ai). Unset or false, nothing reaches those hosts: the templates come from the image and the update check answers with the running version. Set it on the task worker and the scheduler too, which send and schedule the daily usage event.
marketplace_enabledbooleanfalse아니요Lets the server reach Dify's plugin marketplace (marketplace.dify.ai) to install, upgrade and look up plugins. Model-provider plugins such as OpenAI's install from the marketplace, so a Release whose applications use one sets it. Unset or false, nothing reaches that host and plugins install only from an uploaded package or from GitHub. Set it on the task worker and the scheduler too, which run the daily plugin upgrade check.
computeobject—아니요—
overridesobject (open)—아니요Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

출력 계약

이 컴포넌트가 uses 토폴로지를 통해 소비자에게 게시하는 값입니다.

이름타입기본값필수설명
hoststring—예In-cluster DNS name of the Service fronting the console and application APIs. The front end and the workers dial this name for every piece of data they show or act on.
portinteger—예TCP port that Service accepts API requests on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
protocolstring—아니요URL scheme to reach `host` and `port` over, which a consumer composes its base URL on.

uses 소켓

이 컴포넌트가 연결에 사용하는 의존성 소켓입니다. 소켓을 통해 배선되는 모든 연결의 대상은 해당 소켓의 레이블 셀렉터를 충족해야 하며, 각 연결은 소켓이 선언한 슬롯에 첨부를 전달할 수 있습니다. 필수 슬롯은 Aggregate 또는 Release가 해당 소켓을 통해 배선하는 각 연결이 채워야 합니다.

backend

셀렉터
component.aggrega.ai/category=datastore
주입
env

이 소켓을 통한 각 연결이 채울 수 있는 슬롯

슬롯셀렉터필수주입민감설명
credentialfeature.aggrega.ai/kind=secret아니요env예Optional password the server 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 server 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 helm Recipe mounts the whole Secret read-only and points the cache client and the task broker at the file; the compose Recipe refuses it, having no Secret to mount. 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 server 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 server 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 task worker 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 server signs session cookies with it and encrypts stored model-provider credentials under it, and the task worker decrypts them with the same secret. 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 server's internal API, which the server compares against its own. The server and the task worker declare this slot under the same name and the plugin runtime presents it on its connection to the 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.
owner_passwordfeature.aggrega.ai/kind=secret아니요env예Password of the owner account named by infra.owner_email, read only when values.app_definition is set: the step that imports the application at deploy sets it when it performs Dify's first-time setup, and signs in with it. Required then, and the build halts when nothing fills this slot; there is no development default. On helm the step receives it by reference, as a Kubernetes secretKeyRef to the Secret the credential publishes, so the password appears in no file the Recipe renders, and a credential publishing no Secret name and data key halts the build; on compose it receives the value the credential delivers, written into the emitted file as delivered, so an origin written as a Compose variable reference keeps it out of the file. Dify accepts a password of at least eight characters holding both letters and digits.

자체 주입 허용 목록

env

관계

게시된 다른 엔터티와 주고받는 타입 지정 에지입니다. 게시된 대상이 없는 참조는 링크가 아닌 끊어진 에지로 표시됩니다.

사용함

사용됨

Component 개념 레퍼런스 →

Aggrega 카탈로그 — 컴포넌트, 기능, 레시피, 그리고 이를 렌더링하는 플러그인의 공개 인덱스입니다.

공유 Aggrega 디자인 시스템으로 구축되었습니다.

개인정보 보호