Deploy from any Git URL, public or private
Point an existing Voroa service at any https Git repository, public or private with an access token, and keep its URL, variables, databases and deploy history.
A Voroa service can build from any Git repository you can reach over https, not only from a connected GitHub or GitLab account. Use this when your code lives on another Git host, or when your usual connection is unavailable.
Create a new service from a Git URL
You do not need to connect a GitHub or GitLab account for this.
- Click New, then choose the service type: web service, static site, background worker or cron job.
- Under the repository picker, click Deploy from a Git URL instead.
- Enter the https clone URL, the branch, and an access token if the repository is private.
- Fill in the rest of the form as usual and create the service.
Switch a service to a Git URL
- Open the service, then Settings.
- In Source, click Edit, then Use a Git URL.
- Enter the https clone URL, for example
https://git.example.com/team/app.git. - Enter the branch to deploy. It is required.
- For a private repository, enter an access token with read access. Add a username only if your Git host needs a specific one with the token.
- Click Save, then Confirm change. The service redeploys from the new source.
The service keeps its URL, custom domains, environment variables, database connections and deploy history. Only the source changes.
The access token
The token is stored encrypted and is never shown again, not even to you. To replace it, open the same editor, leave the URL and branch as they are, enter the new token and save. If you change the URL without entering a token, the old token is removed, so it is never sent to a different host.
Deploying new code
A Git URL service does not deploy on its own when you push, because Voroa receives no notification from your Git host. Deploy it from the dashboard, or call the service’s deploy hook from your CI after your tests pass.
What is accepted
- https URLs only, on the standard port.
- A public host name. Private or internal network addresses are refused.
- No username or token inside the URL itself. Use the token field.
To go back to a connected GitHub or GitLab repository, open Source, click Use a connected repository and pick one.
Frequently asked questions
Which Git hosts work?
Any host that serves your repository over https on the standard port with a public host name, such as a self-hosted Gitea or GitLab instance, Bitbucket or Azure Repos.
What kind of access token do I need?
A token that can read the repository, created on your Git host. Read access is enough; Voroa only clones your code.
Can I use an SSH clone URL?
No. Only https URLs are accepted.
How do I deploy automatically after a push?
Call the service’s deploy hook from your Git host’s CI after your tests pass.