Skip to main content
This guide explains how to auto deploy static website GitHub projects on ORIV. After setup, every push to your selected branch can trigger ORIV to pull the latest code, run your deployment script, and update the live site.

​
Before you start

  • An ORIV account with a server ready for the site.
  • A GitHub repository containing the static website source or final files.
  • Permission to authorize the repository for ORIV.
  • A known build command and output folder if the repository requires a build step.
Connect GitHub so ORIV can access the repository for deployment.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step-by-step Auto-Deploy Setup Of A Static Website From GitHub On ORIV

​
Step 1: Connect GitHub to ORIV

Open your ORIV settings or site creation flow and connect your GitHub account. Give the connection a clear label if you manage multiple GitHub accounts. Authorize GitHub so repositories can be selected from ORIV.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step 2: Create a site from the repository

Open the target server, create a new site, and choose the Git repository option. Select the repository and branch ORIV should deploy. Choose the repository and production branch for the static site.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step 3: Enable push-to-deploy

Turn on push-to-deploy so GitHub sends a webhook event to ORIV after pushes to the configured branch. Only pushes to that branch should trigger the deployment. Enable push-to-deploy for automatic deployments from GitHub.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step 4: Add the deployment script

If the repository already contains final static files, the deployment script may be minimal. If it needs a build, install dependencies, build, and copy the output folder into the web root.
Set the commands ORIV should run on each deployment.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step 5: Add domain, SSL, and backups

Attach the domain, enable HTTPS, and configure backups before relying on automatic deployments. A backup gives you a rollback point if a bad commit ships to production. Finish the setup with domain, SSL, and backups.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Verify auto-deploy

  1. Make a small visible change in the repository.
  2. Push to the configured branch.
  3. Open ORIV deployment logs and confirm the webhook triggered a new deployment.
  4. Visit the site and verify the change appears.
  5. Use deployment logs to verify every push-to-deploy run.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Rollback or pause deployments

If a deployment ships the wrong version, revert the commit and push again, or restore the site from a known-good ORIV backup. To pause automatic deployments while investigating, disable push-to-deploy in the site Git settings.

​
Troubleshooting

  • If Git pushes do not trigger deployment, confirm push-to-deploy is enabled and the push went to the configured branch.
  • If GitHub webhooks were removed or changed, re-save the Git settings in ORIV so the webhook can be recreated where supported.
  • If the build succeeds but old content remains, verify the script copies the correct output directory into the web root.
  • If environment variable changes do not appear, run a new deployment after saving them.
  • If SSL fails after deploy, debug DNS/SSL separately; deployment and DNS propagation are different parts of the launch.

​
Frequently Asked Questions

​
Can I switch the deployed branch later?

Yes. Change the configured branch in the ORIV Git settings, save, and run the next deployment from that branch.

​
Can I manually redeploy without a Git push?

Yes. Use the manual deployment option in ORIV when you want to rerun the deployment script without changing the repository.

​
Does auto-deploy replace backups?

No. Auto-deploy updates the site, while backups give you rollback protection. Use both for safer releases.

​
How the auto-deploy loop works

  1. You push a commit to the selected GitHub branch.
  2. GitHub sends a webhook event to ORIV.
  3. ORIV pulls the latest code from the repository.
  4. ORIV runs the configured deployment script.
  5. The script copies the final output to the web root.
  6. The next browser request loads the updated version after cache clears.

​
Deployment script patterns

The deployment script should be repeatable. A good script can run many times without leaving old build files, nested folders, or partial output behind.

​
Release safety tips

  • Use a production branch for live deployments.
  • Review changes before merging into the deployment branch.
  • Create backups before major redesigns or build-system changes.
  • Keep deployment logs available when asking for support.
  • Pause push-to-deploy if a bad commit is repeatedly deploying while you investigate.

​
What to send to ORIV Support

  • The ORIV site name and public domain.
  • The GitHub repository/branch label, without private tokens.
  • The time of the last push and whether GitHub shows webhook delivery.
  • The deployment log output from ORIV.
  • Whether manual Deploy Now works while GitHub push-to-deploy does not.
Still stuck? Feel free to contact our support team.