Ingot

Deployment and Operations

field data sources            factory server
control systems / instruments / vision / inspection / business systems
                └─ Edge or data adapter ──────→ Platform API
                                 ├─ PostgreSQL / TimescaleDB
                                 ├─ Optimizer
                                 └─ Platform Web

Deploy Edge near equipment. Platform, database, optimizer, and Web may share one factory server through Compose or be separated behind the same contracts.

Configuration

cp .env.example .env

Change at least:

  • INGOT_POSTGRES_PASSWORD
  • INGOT_EDGE_TOKEN
  • INGOT_ADMIN_PASSWORD

The repository ignores .env; never commit real credentials.

Start

docker compose -f docker-compose.app.yml up -d --build

Enable the field connector profile with:

docker compose -f docker-compose.app.yml --profile connector-host up -d --build

Configure addresses or interfaces, tokens, and mappings before connecting a real data source.

Health

Service Check
Platform /health
Optimizer /ready
Connector /health
Web /health
PostgreSQL pg_isready

Optimizer /ready verifies the PyTorch, GPyTorch, and BoTorch runtime. Platform starts without Optimizer; acquisition and inspection continue while new recommendations remain unavailable.

Data and backup

Back up at least:

  • PostgreSQL volume;
  • inspection attachments;
  • process-knowledge files;
  • Edge event databases until forwarding is confirmed.

A restore drill must verify experiment, cycle, inspection, and evidence relationships—not merely database startup.

Upgrade

  1. back up database and attachments;
  2. read CHANGELOG.md;
  3. run migrations in a test environment;
  4. execute scripts/verify.sh;
  5. update central services;
  6. confirm Edge backlog recovery;
  7. regress observation assembly and suggestion on a known campaign.

Minimum internal-network boundaries

Capability first does not remove basic operational boundaries:

  • do not expose PostgreSQL, Optimizer, or Connector beyond required networks;
  • replace sample secrets;
  • use separate Edge ingestion tokens;
  • back up and restrict attachment storage;
  • require engineering review before experiment execution.