Esta página se tradujo automáticamente. Leer el original en 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.

Versión

1.0.02.0.0

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:9ceb90e88f845b62a2f566f50181e61db591b39af11ead648c09d307951b9788
Publicado
2026-11-15T08:09:34Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • 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

Referencia en esta versión

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

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

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

Workload

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

Variables locales

No se declararon variables locales.

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

  • implementaimplementacontrato compatible

    core/ai-agent/dify:1.1.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad