Deployment targets

A deployment target describes where and how a release should be applied. It is not the agent itself.

Create a target without an agent

Targets may be created before any DinaSync agent is active. Select Targets, create the target, and leave the agent field set to Assign later.

Identity: Display name and pipeline reference such as production_api.
Agent: Optional DinaSync agent assignment.
Strategy: Docker Compose, Docker container, or Docker Swarm.
Configuration: Strategy-specific destination fields.

Docker Compose fields

Working directory: Directory containing the Compose project on the target environment.
Compose file: File passed to the restricted deployment executor.
Image variable: Environment variable that receives the release image.
Project name: Optional Compose project name.
Service: Optional service to update.

At deployment time, DinaSync pulls the requested release and runs Compose with the configured image variable. Paths must be valid absolute host paths under the agent’s restricted execution policy.

Docker container fields

Container name: Existing container identity that DinaSync replaces.
Restart policy: unless-stopped, always, on-failure, or no.
Published ports and volumes: Optional Docker mappings, one per line.
Local environment names: Names copied from the DinaSync host environment without sending their values through Codinamo.
Command arguments: Optional container command, one argument per line and executed without a shell.

Docker Swarm fields

Service name: Existing Swarm service whose image will be updated.
Docker context: Optional Docker context used to reach the selected daemon or Swarm manager.

Revisions

Saving an edit creates a new target revision. A deployment job records the exact revision it received so later configuration changes do not rewrite execution history.

Use from a pipeline

Add DINASYNC_DEPLOY and set its target parameter to the pipeline reference, not the TAR-… identifier. Set release to an image reference exported by an earlier action. The target must be enabled and assigned to an active agent before the action executes.

See Deployment model.