What Is Git Deploy? Deploying From a Repo

Git deploy means your hosting pulls your website's code straight from its Git repository, instead of you uploading files by hand. You push a change to GitHub, GitLab or another Git host, and the site updates. The repository becomes the one place your site's code lives.

How it works

You tell the host the repository's URL and which branch to use. When a deploy runs, the host fetches that branch, copies the files into place, installs dependencies if the runtime needs them, and restarts the app. A deploy can start when you click a button, on a timer, or when your CI system calls a webhook URL after tests pass.

Because every deploy comes from a commit, rolling back is a matter of deploying an earlier commit, and you can always tell what code is running.

When to use it

• Any site whose code is already in Git: PHP, Node.js, Python or static.
• Teams, where several people change the code and deploys should not depend on one person's laptop.
• Deploying automatically after your tests pass in CI.

When not to use it

• A site you edit in its own admin screen, such as most WordPress sites. Content lives in the database, not the repository.
• An app that needs a build step, services or a deploy process the host does not run. A VPS lets you script the deploy yourself.

How it works on VeloxaHost

Git deploy is part of managed web hosting, on every plan.

• Source. A public Git repository over HTTPS, a branch (main unless you say otherwise) and an optional subdirectory, for an app that lives in a folder of a larger repository.
• When it runs. By hand, every hour, every day, or from a CI webhook.
• CI webhook. After you save the settings, the site's page shows a webhook URL. A POST to it queues a deploy of the saved branch, for example from a GitHub Actions step. The URL contains the site's secret token, so keep it in your CI secrets.
• One at a time. Only one deploy runs per site at a time; a webhook call during a running deploy gets a 409 answer.
• What runs. It depends on the runtime. A Node.js deploy, for example, replaces the app's files with the repository, runs npm ci (or npm install without a lockfile) and restarts the app. The Node.js, PHP, Django and static site pages list the exact steps.
• Results. Each deploy is listed under Recent deploys on the site's page.

FAQ

Can I deploy from GitHub?

Yes. Use the repository's HTTPS URL. GitLab, Gitea and other Git hosts work the same way.

Can I deploy from a private repository?

Git deploy is set up for public repositories. For private code, a VPS lets you build your own deploy, for example a CI job that copies files over SSH.

How do I deploy on every push?

Copy the CI webhook URL from the site's page into your CI secrets and call it with a POST after your tests pass.

Does the deploy run my build command?

Not always. A Node.js deploy installs dependencies and restarts the app but does not run npm run build; add a prestart script if your app needs a build. Each framework page says what runs.