Skip to content
EN FR

Deployment and distribution

Documentation status: guide — see Maturity and evidence.

A deployable logiCells application contains more than binaries. Package the declarative model, configuration, views, services and runtime resources as one reproducible assembly.

Deployment tree

Keep these concerns visible:

application/
packages/
models/
views/
services/
resources/
database/
database/clean/
graph/
cache/
log/
temp/
synchronization/
snapshots/
process/
wallets/

Models and views are runtime assets, not only development artifacts.

Environment-specific graph binding

The guide's environment example is retained using normalized public names:

# Development
graphKind: MemoryRichGraph
graphParams: [Workspace]/Graph

# Release
graphKind: PersistentRichGraph
graphParams: [BasePath]/Graph

The conceptual model remains the same across environments; configuration selects the concrete runtime deployment.

Promotion

A production promotion should prove:

  • the same package/manifest/model identities are loaded;
  • required capabilities are available;
  • persistent storage is reachable and compatible;
  • service publication is active only where intended;
  • health/readiness checks distinguish process liveness from usable runtime readiness;
  • logs expose model loading and initialization failures.

Do not package environment secrets into reusable model packages. Environment-specific values such as credentials, endpoints, ports and local paths belong to deployment configuration or secret management.

See DevOps deployment and Runtime readiness.

Full operational walkthrough

For the complete configuration, service, packaging, update, and diagnostic path, continue with Runtime services, packaging, and deployment.