Directories
¶
| Path | Synopsis |
|---|---|
|
Package bundle builds nemo bundles from a compose project, and moves them between registries and OCI layout directories.
|
Package bundle builds nemo bundles from a compose project, and moves them between registries and OCI layout directories. |
|
Package credentials resolves the credentials of an action from their sources, the strategies of a CNAB credential set (cnab-spec 802-credential-sets.md), as Porter writes them:
|
Package credentials resolves the credentials of an action from their sources, the strategies of a CNAB credential set (cnab-spec 802-credential-sets.md), as Porter writes them: |
|
Package docker is the installer's client of the Docker Engine for what every Docker has: a Client that creates, finds and deletes networks, volumes, containers and images from their specs, one file per kind.
|
Package docker is the installer's client of the Docker Engine for what every Docker has: a Client that creates, finds and deletes networks, volumes, containers and images from their specs, one file per kind. |
|
Package installer is the invocation image side of nemo: it reads the operation a CNAB runtime hands to the container and applies the bundle's compose project to the target with the Orchestrator the target names.
|
Package installer is the invocation image side of nemo: it reads the operation a CNAB runtime hands to the container and applies the bundle's compose project to the target with the Orchestrator the target names. |
|
compose
Package compose is the Compose orchestrator: it applies a compose project to one Docker as plain containers, the way docker compose up --wait does, and labels them the way docker compose does, so that docker compose ps and logs still see them.
|
Package compose is the Compose orchestrator: it applies a compose project to one Docker as plain containers, the way docker compose up --wait does, and labels them the way docker compose does, so that docker compose ps and logs still see them. |
|
compose/convert
Package convert turns a compose project into what the Compose orchestrator creates on the Docker Engine: the create options of each container, its networks and volumes, and the state to wait for, the way docker compose does.
|
Package convert turns a compose project into what the Compose orchestrator creates on the Docker Engine: the create options of each container, its networks and volumes, and the state to wait for, the way docker compose does. |
|
swarm
Package swarm is the Swarm orchestrator: it applies a compose project to a swarm as services, the way docker stack deploy does, and waits until they converged.
|
Package swarm is the Swarm orchestrator: it applies a compose project to a swarm as services, the way docker stack deploy does, and waits until they converged. |
|
swarm/convert
Package convert turns a compose project into the specs of Swarm objects, the way docker stack deploy does (docker/cli, cli/compose/convert).
|
Package convert turns a compose project into the specs of Swarm objects, the way docker stack deploy does (docker/cli, cli/compose/convert). |
|
Package labels holds the labels nemo puts on everything the installer creates.
|
Package labels holds the labels nemo puts on everything the installer creates. |
|
Package nemo is nemo's API.
|
Package nemo is nemo's API. |
|
Package progress is how long operations report what they do.
|
Package progress is how long operations report what they do. |
|
Package runtime runs the actions of a bundle's installations, as a CNAB runtime: it builds the claim, hands the operation to the driver that runs the invocation image, and returns the claim, its result and its outputs.
|
Package runtime runs the actions of a bundle's installations, as a CNAB runtime: it builds the claim, hands the operation to the driver that runs the invocation image, and returns the claim, its result and its outputs. |
|
Package stack is the desired state of a stack: the target, the installer, and the installations to make there, by their spec: a bundle, its parameters and the sources of its credentials.
|
Package stack is the desired state of a stack: the target, the installer, and the installations to make there, by their spec: a bundle, its parameters and the sources of its credentials. |
|
Package storage keeps what nemo knows of its installations, as Porter keeps it: an Installation, its spec and how its last action went, and for each action its Run, the CNAB claim with the bundle it ran, its Result and its outputs, documents of cnab-spec 400-claims.md.
|
Package storage keeps what nemo knows of its installations, as Porter keeps it: an Installation, its spec and how its last action went, and for each action its Run, the CNAB claim with the bundle it ran, its Result and its outputs, documents of cnab-spec 400-claims.md. |
|
file
Package file is a store in a local directory, one per installation, in the directory of its stack, next to the stack's manifest:
|
Package file is a store in a local directory, one per installation, in the directory of its stack, next to the stack's manifest: |
|
volume
Package volume keeps the records of a stack's installations in a volume of its target, where whoever reaches the target finds them: the CI that deployed the stack, and anyone who imported its manifest.
|
Package volume keeps the records of a stack's installations in a volume of its target, where whoever reaches the target finds them: the CI that deployed the stack, and anyone who imported its manifest. |
|
Package target describes where a bundle is deployed, and where its installer runs.
|
Package target describes where a bundle is deployed, and where its installer runs. |
|
Package transfer carries a bundle's images into the target's daemon, with no registry in between.
|
Package transfer carries a bundle's images into the target's daemon, with no registry in between. |
Click to show internal directories.
Click to hide internal directories.