How to change your deploy branch or root directory on Voroa
Change which Git branch Voroa deploys, or point a service at a subfolder of a monorepo, from Settings. Fix a wrong branch or path and redeploy in one click.
Every Voroa service deploys from one branch of your repository, and builds from one root directory inside it. You can change both at any time from Settings — useful when you switch deploy branches or move an app into a subfolder.
Branch
The branch is the line of your repository Voroa builds and deploys. When automatic deploys are on, only pushes to this branch trigger a new build.
Root directory
The root directory is the folder Voroa builds from.
- Use
/when your app lives at the repository root. - Use
/subfolderfor a monorepo — for example/frontendor/apiwhen a single repository holds several apps.
Voroa expects your app’s manifest, such as package.json or requirements.txt, to be inside the
root directory you choose.
Pick a folder from the list
For a repository connected through GitHub, the Root directory field lists the repository’s
folders as you type. Folders that hold app files, such as a package.json or requirements.txt, are
marked app found. You can always type a path yourself instead.
When you create a service and the top of the repository has no app files, but exactly one folder does, Voroa fills that folder in for you and says why. It never replaces a path you typed. In Settings, Voroa only suggests the folder, with a Use button, and changes nothing until you save.
Change branch or root directory
- Open the service and go to Settings.
- Under Source, edit Branch and Root directory.
- Select Save.
Saving redeploys your service from the new branch and directory so the change takes effect. You can watch the new build in the Deploys tab.
Changing the repository itself
To point the service at a different connected repository, see change the repository. The branch is re-checked against the new repository when you do.
Fixing a wrong setting
If a deploy fails because the branch or root directory was wrong — for example a build that reports it could not detect your app — just correct the field here and save. There is no need to recreate the service.
Frequently asked questions
Can one repository run several services?
Yes. Create one service per app and give each its own root directory, for example /api and
/web. Use build filters so a push rebuilds only the service it changed. See
monorepo support.
Can I deploy a feature branch to test it?
Turn on pull request preview environments to get a separate live copy for each pull request, instead of switching your main service’s branch.
Why does my build say it could not detect the app?
The root directory usually points at the wrong folder. Pick the folder marked app found in the list, save, and the service redeploys.