Deploy from an image and Git

Deploy from an image

zenifra project image set --project <project-id> --image ghcr.io/zenifra/app:1.2.0

Always prefer a fixed version tag over latest.

Projects can use a Git source from a supported provider (GitHub or Forgejo). An organization owner creates the connection in the Console; the CLI lists and uses existing connections and never asks for or shows provider credentials.

Check providers, runtimes, and connections, resolve the repository by path, and list branches:

zenifra git providers
zenifra git runtimes
zenifra git connections
zenifra git repositories resolve --connection <connection-id> --path team/application
zenifra git branches --connection <connection-id> --repository <repository-id>

The ID returned by resolve belongs to that connection. Use the IDs in config.source and config.build when creating the project (see examples/http-git-project.json):

zenifra create project --name api-web --plan basic --payment-mode hourly --config @examples/http-git-project.json

Inspect and change the project's source and deploy mode:

zenifra project source --project <project-id>
zenifra project source branches --project <project-id>
zenifra project source deploy-settings set --project <project-id> --mode branch
zenifra project source deploy-settings set --project <project-id> --mode tag --tag-pattern "v*"
zenifra project source deploy-settings set --project <project-id> --mode release --tag-pattern "v*" --include-prereleases true

Modes are manual, branch, tag, and release. tag and release require --tag-pattern (* and ? wildcards); --include-prereleases only applies to release and defaults to false. Avoid changing the source at the same time from the Console or another client.

Projects with a legacy GitHub configuration keep using zenifra project github and zenifra project github deploy-settings set, with the same modes.

Trigger and follow builds

zenifra deploy --project <project-id> --branch main
zenifra deploy watch --project <project-id> --build <build-id>
zenifra builds --project <project-id>
zenifra builds logs --project <project-id> --build <build-id> --follow
zenifra deployments --project <project-id>

zenifra deploy triggers the Git build/deploy and returns a build_id. deploy watch follows the status and prints incremental logs until the final state, which is handy in pipelines. Log differences:

zenifra project logs: the running application
zenifra builds logs: the Git build pipeline
zenifra deploy watch: status + logs of a specific build

Deploy from an image and Git