MarvX
Help Center

Deploying

Preview deployments

Build any branch or GitHub pull request as its own container with its own URL, without touching production.

A preview builds one branch as a separate container with its own URL; production keeps running.

Requirements: the project has deployed successfully once and builds from Git (not Deploy from Image).

Manual previews

  1. Project Preview Deployments tab, type a branch (e.g. feat/billing), Deploy preview.
  2. Status goes building → running (or failed with the error). The URL looks like https://<project>-<id>-pv-<branch>.apps.marvx.io.

Deploying the same branch again rebuilds that preview.

Automatic previews from GitHub pull requests

With GitHub, Autodeploy on and the webhook connected: opening, reopening or pushing to a PR builds a preview of its head branch; closing or merging removes it.

Configuration

Previews use production's repository, build type and environment variables, on the preview branch. Volumes, published ports, custom domains and your plan's memory setting aren't applied (platform default memory).

Because previews share production variables, they connect to the same database and services. If that's risky, have your app behave differently on preview branches or use credentials safe to share.

Remove and billing

Remove a preview from the tab; its container and URL are deleted. Previews don't use your monthly deployment allowance but are blocked while the workspace is suspended or a payment is overdue.