Develop and Deploy

Every app has source code and a build history. Open an app, then use its Source section to choose the development workflow.

Built-in workflow

Use Airlock’s built-in coding workflow for quick changes. The system assistant can help create apps and manage Airlock resources through your existing permissions.

For larger changes, use the local workflow so your coding harness can work in the app repository directly.

Air CLI workflow

For an app without a Git remote, the Source section provides instance-specific commands to:

1. Install the Airlock launcher.
2. Clone the app source from Airlock.
3. Log in to the Airlock instance.
4. Deploy a local build.

Run the provided commands from your development machine. Inside the cloned repository, use go tool air deploy -m "Describe this deployment" after testing your changes.

Git workflow

Connect a remote repository from the app’s Source section when your app already has a Git-based workflow.

Airlock stores the remote, branch, and credential binding. The section also shows a webhook URL and secret for push-triggered updates. In read-only mode, the remote remains authoritative. In read/write mode, Airlock may push changes it makes back to the remote.

Builds and failures

Every initial deployment, upgrade, or source update creates a build. Open Activity to inspect build progress, logs, and failures.

An app that fails to build is marked failed until you fix the source and deploy or upgrade it again. Existing active source and data are preserved across normal container restarts.