mait.sh1.78.0

Private beta: features and content may change. No warranty; use at your own risk.

Docs / On-premise servers

AIDC Hub

Serve development-tool packages to your AIDC clients.

For organizations that serve development-tool packages to their own AIDC clients, and the operators who deploy the hub.

Read from the top for the basics; the later sections go deeper.

Beta
All components

What it doesBasics

AIDC Hub is a package server you run yourself. Package authors publish archives and manifests to it with AIDC Pack; the hub signs each one and serves the catalogue and downloads to AIDC clients. Every protected request carries the caller's credentials, and each operation needs its own feature.

Where your organization's packages come from
Package authorsPublish archives and manifests with AIDC Pack.
AIDC HubStores and signs packages, serves catalogue and downloads.
AIDC clientsInstall the packages your projects name.
Illustrative. Run one hub per data volume; health alone does not test credentials.
  • Publish archives and manifests in one request or in resumable chunks; the hub signs each one
  • Serve the package catalogue, exact-variant metadata and downloads to `aidc`
  • Grant browse, download, publish and unpublish separately through credential features
  • Commands for key rotation, version refresh, integrity checks and package retention

First useBasics

  1. Prepare a server certificate bundle, the credentials-service setting from your on-premise setup and a data volume.
  2. Start the hub as a container or with its Helm chart, with the hub terminating TLS itself or behind a gateway.
  3. Check GET /health, then an authenticated request for the catalogue and the hub key.
  4. Publish a package with AIDC Pack and install it with aidc.

CommandsAdvanced

$ aidc-server version
$ aidc-server keys status
$ aidc-server consistency check
$ aidc-server prune keep-recommended

Good to knowHelp

  • Run one instance per data volume: the package database accepts one writer.
  • Every protected request needs the credentials service to confirm the account and credential; health does not test that.
  • A healthy response proves only that the server answers; check an authenticated catalogue and key request.