Skip to content

DeployBy INZOX Cloud teamPublished 2 min read

Deploy from Git without managing a server

In short

In INZOX Cloud you connect a Git repository to a project, and every push to the chosen branch deploys a new version. You can read the deployment logs and roll back to an earlier version. Hosting runs through the hosting platform your workspace is configured with.

What “deploy from Git” means

Deploying from Git means your repository is the source of truth. You do not copy files to a server. You push a commit, and the platform fetches that commit, builds it, starts the new version and retires the old one.

The benefit is repeatability: the same commit always produces the same release, and every release is tied to a commit you can read.

What it does in INZOX Cloud

  • You create a project and add a website or an application to it.
  • You connect a Git repository to that application.
  • A push to the connected branch triggers a deployment (deploy on push).
  • Each deployment keeps a log you can read from the console.
  • You can roll back to an earlier deployment if a release misbehaves.
  • Environment variables are set in the console, so secrets stay out of your repository.

Setting it up, step by step

  1. Create a project and add your application or website.
  2. Connect the repository. For a private repository, add the public deploy key the console shows you to the repository as a read-only deploy key.
  3. Set the environment variables your application needs, such as a database connection string.
  4. Push a commit to the connected branch.
  5. Open the deployment and read its log until it finishes.
  6. If the new version is wrong, roll back to the previous deployment.
git add .
git commit -m "Update the pricing page"
git push origin main

Rolling back safely

A rollback redeploys an earlier release. It is fast because the earlier version is already known to work, and it does not change your repository. Fix the problem in a new commit afterwards.

Be careful with databases: a rollback restores application code, not data. If a release changed your database structure, check that the earlier code still works with it before you roll back.

What you still own

  • Your repository and its history. It stays yours, in your own account.
  • Your application's build settings and environment variables.
  • Backward-compatible database changes, if you use a database.

To see the other half of going live, read how to connect your own domain.

Questions and answers

Do I need to manage a server to deploy from Git?
No. You connect a repository to a project in the console and push. The platform builds and runs the release for you.
Can I roll back a deployment?
Yes. You can redeploy an earlier release from the console. A rollback restores application code, not database data.
Does the free plan support deployment from Git?
Yes, for one static website on a generated web address. Your own domain needs a paid plan.