Deploy from your own CI

Set it up

1. Create the app from a connected GitHub repository (Quickstart). A repository added by its public URL, or one on GitLab, cannot deploy from CI.
2. In the app’s Settings → Builds, choose Deploy from my own CI instead. homeport stops building pushes to that environment’s branch. Let homeport build it switches back.
3. Add a workflow that builds the binary and runs the action, on the branch the environment follows.

The workflow

name: Deploy
on:
  push:
    branches: [main]

permissions:
  id-token: write     # mint the OIDC token
  contents: read

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: oven-sh/setup-bun@v2
      - run: bun install --frozen-lockfile
      - run: bun build --compile --target=bun-linux-x64 ./src/index.ts --outfile server

      - uses: homeport-sh/deploy@v1
        with:
          artifact: ./server

For Go, build with CGO_ENABLED=0 GOOS=linux go build -o server . and pass the same artifact. The permissions: id-token: write line is required: without it the job has no token to sign in with.

Which app it deploys to

There is no app to name. The deploy lands on the environment that follows the branch the run is on: main to production, staging to staging. Only a repository that holds several apps on the same branch needs app:, set to the app’s name.

The token is checked against the repository and branch: a run from another repository, or from a branch no environment follows, is refused. Runs on GitHub-hosted runners are accepted.

Inputs

The action sets two outputs, deployment-id and status.

What you deploy

• One Linux executable (ELF), for the architecture of the machine your app runs on. A macOS or Windows build is refused.
• Up to 512 MB.
• Its environment variables still come from homeport, set on the Variables tab. Your workflow never sees them.
• It runs the same way as one homeport built: on $PORT, with its health check, and with the run, release and processes of the app.

For a static site, use homeport’s own builds or upload it: the action deploys binaries.

When it fails