Halaman ini diterjemahkan oleh mesin. Baca versi asli dalam bahasa Inggris.

Component

core/compute/server

A generic long-running server primitive. It adds no fields of its own; what it contributes is its operational type, `server` — long-running, stateless compute that expects inbound application traffic. An Aggregate declares this for a component that stays up and serves requests, rather than `worker`, with zero inbound application ports, or the run-once `task`. Declaring no `provides`, it publishes nothing across an edge. On a Kubernetes cluster it is a Deployment behind a ClusterIP Service. In an AWS account with an ECS cluster and a VPC, terraform/server-ecs and cloudformation/server-ecs run it as an Amazon ECS service on Fargate. In a Google Cloud project with a VPC network, terraform/server-cloud-run runs it as a Cloud Run service; in an Azure subscription with a Container Apps environment, terraform/server-container-apps as a container app. On Docker Compose, compose/server runs it on the host's loopback address. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The image is the Release's own code, so an edge from this component delivers what its `inject:` block dictates, and no declared socket narrows the mechanism: `env` entries become variables on every realization, `file` entries files everywhere but on Amazon ECS and Cloud Run, and `arg` or any other mechanism is refused by name, as no realization renders a command line. The component's own `inject:` block takes `env` entries too. A `core/secret-value` attachment's value is written into the rendered workload in the clear on every realization; no realization delivers `core/referenced-secret` or `core/random-password` to it, and the helm realization refuses either by name.

Versi

1.0.01.1.0

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:188fd63b3c97337677995fff85642c14871f6c0b72b803a22e2c5a76b11107c7
Dipublikasikan
2026-11-10T10:10:16Z
Identitas penandatangan
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Tanda tangan

  • Resmiapplication/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:757ed54d71cf28e4ef2aabd0b524eabc8ced40dffe55a3447b8c57e348a38d50

Referensi pada versi ini

oci://hub.aggrega.ai/component/core/compute/server:1.0.0

Parameter pengembang

Nilai yang ditetapkan pengembang di Aggregate.

Memperluas BaseComponents#/schemas/BaseComponentParameter

Penentuan ukuran oleh operator

Ukuran infrastruktur yang disesuaikan operator untuk setiap lingkungan.

NamaTipeBawaanWajibDeskripsi
imagestring—tidakContainer image serving the application.
portinteger (min 1024, max 65535)8080tidakPort the container listens on. On Kubernetes the fronting Service carries inbound traffic to it; on Amazon ECS it is the container port a load balancer target group the Release names sends traffic to; on Cloud Run it is the port requests are sent to, which the container is also handed as PORT; on Container Apps it is the ingress's target port, which the container is also handed as CONTAINER_APP_PORT; on Docker Compose it is also the port published on the host's loopback address.
replicasinteger (min 1)1tidakReplica count, the number of tasks on Amazon ECS, of instances on Cloud Run and of replicas on Container Apps, up to 300 there. The floor is one, because a server that expects inbound traffic has nothing to hold a request while it is at zero. Docker Compose runs one container and refuses a count above one.
computeobject—tidak—
overridesobject (open)—tidakProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads: the Amazon ECS realizations read the cluster, subnets, security groups and roles the service runs under, each under its target's own spelling (subnet_ids on terraform, Subnets on CloudFormation), the Cloud Run realization the project, region, VPC network and service account the service runs in, the Container Apps realization the environment and resource group the app runs in and the identities and registry it pulls with, and the Kubernetes and Docker Compose realizations read none of its keys.

Kontrak keluaran

Nilai yang dipublikasikan komponen ini kepada konsumen melalui topologi uses.

Tidak ada nilai keluaran yang dideklarasikan.

Soket uses

Soket dependensi yang menjadi jalur koneksi komponen ini. Target setiap koneksi yang dihubungkan melalui sebuah soket harus memenuhi selektor labelnya, dan setiap koneksi dapat membawa lampiran pada slot yang dideklarasikan soket tersebut. Slot wajib harus diisi oleh setiap koneksi yang dihubungkan oleh Aggregate atau Release melalui soket tersebut.

Tidak ada soket uses yang dideklarasikan.

Slot lampiran

Titik pengikatan bernama tempat sebuah Feature dilampirkan ke komponen ini. Selektor sebuah slot membatasi Feature mana yang dapat mengisinya, dan daftar injeksinya menyebutkan cara materi Feature dapat dikirimkan. Slot wajib harus terikat pada setiap instans, melalui lampiran pada instans tersebut atau pada cakupan di atasnya, dan slot sensitif dideklarasikan untuk menangani materi rahasia. Sebuah Feature juga dapat dilampirkan dengan nama yang tidak dideklarasikan oleh slot mana pun.

Tidak ada slot lampiran yang dideklarasikan.

Daftar izin injeksi mandiri

env

Relasi

Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.

Menggunakan

Digunakan oleh

Referensi konsep Component →

Katalog Aggrega — indeks terbuka berisi komponen, fitur, resep, dan plugin yang merendernya.

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi