← Documentation

Deploy from GitHub

Point an app at a GitHub repository and Anyport builds it and ships it. After the first setup, pushing is the deploy.

Connecting GitHub

You connect GitHub once per organization by installing the Anyport GitHub App and granting it access to the repositories you want to deploy. An organization can hold more than one installation, so repositories spread across several GitHub accounts can all be deployed from the same place.

Anyport only sees the repositories you grant.

Creating an app from a repo

  1. In a project, create an app and choose Deploy from GitHub.
  2. Pick the repository and branch.
  3. Configure the build, then create the app.

Anyport builds the image and rolls it out. The build runs on your own server, not on ours—which is why there is no build-minute charge and no queue to wait in.

Auto-deploy on push

Auto-deploy is off when an app is created, so the first deploy is always one you asked for. Turn it on from the app's Source settings and pushing to the connected branch then triggers a build and rollout on its own. Each deployment records where it came from: the commit, the branch, and whether it was triggered by a push, a manual run, or a redeploy.

The commit that leaves your terminal is the commit named on the row that goes live. The revision it replaces goes quiet in the same beat.

Leave it off per app if you'd rather deploy deliberately.

Rapid pushes

If several pushes land while a build is already running, Anyport does not start a build for each one. Pushes to the same app coalesce, so you get a build of the newest commit rather than a backlog of stale ones.

When a connection breaks

If the GitHub App is uninstalled or loses access to a repository, Anyport pauses auto-deploy for the affected apps rather than repeatedly failing. Restore access and it resumes.

Deploying an existing image

If you already build images in your own CI, skip the repository connection and deploy the image directly. You keep your pipeline; Anyport handles the rollout, revisions, and rollback.

Watching a deployment

Every build and rollout for an app appears in one timeline—what shipped, from which commit, and when. If a release misbehaves, roll back to any previous revision from the same place. See Apps.

Next steps

  • Preview environments — What the same connection gives a pull request.
  • Apps — Scale, health checks, variables, and rollback.
  • Projects — Where apps live.
  • Quick start — End to end, from sign-up to first deploy.