Projects

A project connects your Git repository to Nebion and gives you automatic PR environments with unique URLs.

What You Get

Auto PR Deploys

Every pull request gets its own isolated environment

Unique URLs

Each environment at pr-{number}.{domain}

Webhook Integration

GitHub, Bitbucket, and Gitea

Environment Variables

Pass configuration to your containers

Basic Auth

Password-protect your PR environments

Health Monitoring

Server status and deployment tracking

Create a Project

1. Click New project from the Projects page
2. Fill in your project details:

Field	Description
Title	A name for your project
Repository URL	SSH clone URL (e.g., git@github.com:org/repo.git)
Recipe	Deployment strategy: Docker (default) or Manual (details). Cannot be changed later.
Domain	Base domain for PR environments (e.g., myapp.example.com)
Servers	Assign a Production and/or Development server

3. Click Save — Nebion generates a webhook URL, secret, and deploy key automatically

Connect Your Repository

1. Add the Deploy Key

   On your project's Overview tab, expand Setup and copy the Deploy Key. Add it to your Git repository as a read-only deploy key.

2. Configure the Webhook

   Copy the Webhook URL and Webhook Secret from the Setup section. Add them to your repository's webhook settings. Keep the secret secure — do not commit it to your repository.

   Provider-specific guides: GitHub | Bitbucket | Gitea

3. Create a Pull Request

   Open a pull request in your repository. Nebion automatically creates an environment and deploys your code. Check your project page to see the new environment at pr-{number}.{domain}.

Project Dashboard

Your project page has five tabs:

OverviewConfigureSettingsVariablesFiles

Overview

The Overview tab is your project's status dashboard.

Header shows the repository URL and base domain.

Status strip shows server health and the latest deployment at a glance. Click View full status to expand a detailed panel with three columns:

Section	Shows
Servers	Development and production servers with IP addresses
Configuration	Domain prefix setting, custom variable count, attached file count
Recent Deploys	Last 3 environments with success/error status

Integration status shows whether your webhook is configured. Expand Setup to access your Webhook URL, Webhook Secret, and Deploy Key — each with a Copy button. The project owner can also Regenerate the webhook secret there — see Rotating the webhook secret.

Environments lists all PR environments belonging to this project. Click Add environment to create a manual environment, or open a pull request for automatic deployment.

Configure

Edit your project's core settings:

Field	Description
Title	Rename your project
Region	Select a geographic region (if applicable)
Repository URL	Read-only after creation
Domain	Base domain for PR environments
Production Servers	Assign production servers
Development Servers	Assign development servers

Settings

Domain prefix — when enabled, PR domains include a project ID prefix: p{id}-pr-42.domain.com instead of pr-42.domain.com. Useful when multiple projects share the same domain.

Basic Auth — password-protect your environments with HTTP access control. Environments created after you enable it ask visitors for the username and password; existing environments keep their own setting, which you can change on each environment's Settings tab.

Number of environments — the maximum number of environments (pull request and manual) the project may have, 20 by default. Only a Nebion administrator can change it. The environments list on the project page shows the current usage, for example Environments: 5/20; at the limit Add environment is disabled and new pull requests do not get an environment until one is deleted.

Variables

Manage environment variables that are passed to your containers. See Environment Variables for full details.

• System Variables (read-only) — managed by Nebion, prefixed with nebion_
• Custom Variables (editable) — your own key/value pairs for database credentials, API keys, feature flags, etc.

Files

File management has moved to the Server settings page.

Deleting a Project

1. Open the project's Configure tab
2. Click Delete at the bottom of the form
3. Confirm the deletion

A project without environments is deleted right away. Otherwise its environments are deleted first — exactly as if you clicked Delete Environment on each of them — and the project disappears automatically once the last one is gone. Until then, the project page shows that the deletion is in progress.

• Protected environments are deleted too: the confirmation lists them and asks you to tick a checkbox.
• The deletion can't start while an environment is deploying — wait until the deployment finishes.

WARNING

Deleting a project deletes all its environments, with their containers and data. Servers are kept. This cannot be undone.