Uniac quickstart

Example application

This example starts with an application whose root Dockerfile builds a service listening on 0.0.0.0:8080. The machine has the Uniac CLI, a running Docker daemon, and account access. It uses a new project named my-app, supplies its application description directly, and binds the local project to that remote destination. The following uniac.yaml declares one service and exposes its HTTP port:

runtime: yaml
resources:
  api_definition:
    type: service
    build: .
  api:
    type: deployment
    from: api_definition
    public_ports: [{ port: 8080, type: http }]

The api deployment declaration instantiates api_definition as the service api. Composition in YAML describes the file format and instantiation rules.

Destination and deployment

With that application and manifest in the current directory:

uniac plan
uniac project create my-app
uniac link my-app
uniac deploy
uniac status

An existing project can be linked by name or slug instead of creating one. The project-selection contract also describes selection during deployment and target overrides. The CLI reference defines these commands’ requirements and completion behavior.

Application address

The HTTP address in the service’s endpoint row is this application’s public URL. Output and errors describes the report; Service defines what the observed state establishes.

​Example application

​Destination and deployment

​Application address

Example application

Destination and deployment

Application address