Esta página foi traduzida automaticamente. Leia o original em inglês.

Recipe

dify

The Dify API and console server on Kubernetes via the helm provider's Workload synthesis: a stateless Deployment and a ClusterIP Service on the API port. The identities its uses-edges resolve compose its connection settings and the in-cluster URLs of its siblings, and its outbound requests to a user-supplied address leave through the proxy. A cache publishing valkey-tls or redis-tls is reached over TLS; another TLS protocol halts the build, and so does a vector-store connection whose target is not a vector engine served over http. By default nothing reaches Dify's vendor from it: infra.telemetry_enabled allows the install event, update check, template lists and Creators Platform, and infra.marketplace_enabled the plugin marketplace. infra.console_url sets the console origin. Its application secret comes from the credential attached to secret_key, which has no default: the Component requires the slot, and the build halts when nothing fills it. Each of its other four credentials comes from a credential when one is attached and otherwise from a pinned development literal; the three it presents to the backend, the sandbox and the plugin runtime are held on those connections. Those defaults are for evaluation and local development. The two keys the server shares with the task worker and the plugin runtime are attached on all three or on none. An app_definition, when set, is carried in a ConfigMap and imported by a one-shot Job running the server's image: it performs Dify's first-time setup if needed as infra.owner_email, with the owner_password credential read by secretKeyRef, signs in, and imports the application unless one of that name is present. With no definition, neither is rendered.

Versão

1.0.02.0.0

Procedência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como publicador oficial.
Digest do conteúdo
sha256:9ceb90e88f845b62a2f566f50181e61db591b39af11ead648c09d307951b9788
Publicado
2026-11-15T08:09:34Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • Oficialapplication/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:e206b4d5d8e6df0339e978878bda20d25bad411815f304cf4180000e2f1345c9

Referência nesta versão

oci://hub.aggrega.ai/recipe/helm/dify:2.0.0
Destino
—
Implementa
core/ai-agent/dify:1.1.0

Fornece

Modelos de ponteiros determinísticos que esta receita liga para os consumidores.

NomeModelo
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
protocolhttp

Workload

Workload · form: stateless · replicas: 1 · containers: main

Variáveis locais

Nenhuma variável local declarada.

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.

Usa

  • implementaimplementacontrato compatível

    core/ai-agent/dify:1.1.0

    Todas as saídas obrigatórias são atendidas e cada saída fornecida é nomeada no contrato.

Usado por

Nada no catálogo depende desta entidade.

Referência do conceito Recipe →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design compartilhado do Aggrega.

Privacidade