Build and deployProjects
Project settings
Rename a project, pause and resume it, move it to another team, delete it, and what its workload and region mean.
A project's Settings page has its General, Build, Git, Deployment protection and Advanced settings. Settings save as you change them; the page says "All changes saved". Owners and admins change settings; "Viewers can look but not change settings", and neither can members.
Changes to how a project builds apply from the next deployment. See build settings for the Build section and Git providers for the Git section.
Rename a project
Change Project name under General. The project's slug is its name in lower case with hyphens, and the slug is its free address, so renaming changes the address too: storefront.theorbits.app becomes shop.theorbits.app. Deployment and branch addresses change with it. Update anything that links to the old address.
The slug must be unique across all of Orbits: if another project has it, the rename is refused and you pick another name. A slug is 3 to 40 characters of lower-case letters, digits and hyphens, starting and ending with a letter or digit; a few reserved words can't be used.
Custom domains aren't affected by a rename.
Pause and resume
Under Advanced, Pause the project with the Paused toggle: "Visitors see a paused page and nothing deploys until you turn it back on. Domains and data stay."
While a project is paused:
- its production address, previews and custom domains answer 503 with Orbits' paused page;
- its apps stop;
- nothing deploys, from pushes or by hand.
Its domains, variables, deployments and the builds production can come back to are all kept. Turn Paused off and production is served again within moments.
$ orbits projects pause # the folder's linked project$ orbits projects resumeTransfer to another team
Under Advanced, Transfer moves the project to another team. Pick the team under Move to. You need to be an owner or admin of the project's team, and an owner of the team it moves to ("You need to be an owner there"). If you don't own another team, there's nowhere to move it.
The project keeps its name, slug and free address. Its deployments, environment variables and alerts go with it. Members of the old team who aren't in the new one lose access to it.
Things to check after a transfer:
- Git. Pushes reach a project through its team's Git connection. Connect the same provider, with access to the repository, in the new team.
- Custom domains. Domains belong to a team. Check the project's Domains page in the new team, and add any domain it should serve there.
API tokens can't transfer projects; it needs a signed-in person.
Delete a project
Under Advanced, Delete project "Deletes every deployment, variable and log. Domains are detached, not deleted. This can't be undone."
The dialog counts what goes: deployments and their build logs, environment variables, flags and their history, and the domains that will be detached. Type the project's name to confirm.
Its custom domains stay in the team's Domains and DNS, shown as not in use, ready to point at another project.
$ orbits projects delete storefrontDeleting is for owners and admins. It runs as an operation.
Workload
The workload is how the project runs: static, function, app, worker or container. It's set when the project is created, from the framework unless you choose one, and can't be changed afterwards. To run the same repository another way, create a new project from it. See workloads.
On Free, server frameworks run as app; the function workload is part of Pro.
The Functions section's Time limit and Memory aren't applied yet.
Region
Every project runs in Abuja (abj-1), the only region. The Region field shows it and has nothing else to choose. See region.
Notifications
A project uses its team's notification settings. Team notification settings on the project's Settings page leads there. See notifications.
Through the API
Getting and changing a project, pausing, transferring and deleting it are in the projects API.