Git, builds and auto-deploy

Add a repository

Under Deployment Management → Git, click Add repository. Enter a name, the provider (GitHub, GitLab, Azure DevOps or Bitbucket), the HTTPS clone URL and default branch. Private repositories need an access token. PS-pocketEdge checks it can read the repository before saving.

Import a Compose file

Choose Import Compose file on a repository, pick a branch or tag and the path to the Compose file, and preview it before importing. Imported files stay linked to Git: use Sync from Git to pull in the latest commit.

Deploy from a Dockerfile

If a repository has a Dockerfile but no Compose file, choose Deploy from repository. Enter a name, the branch, the build context and Dockerfile path, the container and host port, environment variables and a server. PS-pocketEdge generates the Compose file for you, builds the image on the server and starts it. The server must have builds allowed.

Builds

Compose files that use build: are built on the target server before deploying. Builds only run on servers enrolled with --allow-builds, one at a time per server. Follow them live in the deployment's Builds tab; you can copy the log or cancel a build there.

To publish a successful build, open it and choose Push to registry, then pick a registry and repository path. The deployment keeps using its local image.

Redeploy on every push

Open Webhook setup on a repository and add the webhook URL and secret to your Git host. After that, every push re-syncs linked Compose files and redeploys any deployment with Redeploy automatically on Git push turned on.

Git report

Open Deployment Management → Git report to see undeployed commits by deployment, or compare the same app across environments. Expand rows or open environment cells for commit details, then export the filtered view as CSV. Follow the Git reports guide below for a worked example.

Example: move one app through environments

1. Add your HTTPS repository and import its compose.yaml from main. Name the saved file orders-api.
2. Deploy that same saved Compose file to staging and production, choosing an environment for each deployment. Use separate servers if both expose the same host port.
3. Push a change to main. If automatic redeploy is off, the existing deployments continue running their recorded commits.
4. Open Git report and click Check now. Review the Behind rows and the By environment comparison before updating a deployment.

The repository and compose.yaml path in this example must exist in your own project. For Dockerfile builds, the target server must allow builds. Webhooks only trigger redeploy for deployments where automatic Git redeploy is enabled.