Create a project and provision Odoo

Create the project

Open Projects, select Create project, and provide a name, lowercase slug, Odoo version, and edition. The slug becomes part of generated resource names and hostnames, so use a stable identifier rather than a temporary release name.

Choose Community or Enterprise based on the code and licensing you are entitled to operate. Tnion.SH does not grant an Odoo Enterprise license or repository access.

Understand the three environments

Every project creates three draft instance records:

• Production: live business use
• Staging: release verification and acceptance
• Development: integration work

These are separate operational targets. Each can be assigned to an appropriate registered server and can map to a different Git branch.

For the first deployment, start with Development. Do not use Production as the place to discover missing server privileges, firewall rules, or module dependencies.

Assign a server

Open the Development instance and select a server that has passed its connection test. Review the generated hostname and database name before saving.

The server must have enough available capacity for the instance and its backups. Tnion.SH allocates instance ports on the selected host and prevents a draft instance from being provisioned without a server.

Provision the instance

Select Provision. The request creates a tracked deployment and starts the remote workflow. Provisioning can install Docker when it is missing, writes the Compose and Odoo configuration, starts PostgreSQL, initializes Odoo, starts the application, and configures the Nginx site.

Follow the deployment log. Do not start a second operation while an instance deployment is active. A failure remains recorded so you can inspect the last successful step and error.

Complete the first run

After the instance reaches Running:

1. Open its endpoint from the console.
2. Confirm that the intended database opens.
3. Record the generated Odoo administrator credential in an approved password manager.
4. Review the Odoo and deployment logs for startup errors.
5. Create a manual backup before introducing important configuration.

Use start, stop, and restart for routine service control. Use a Git deployment when the project is connected to a repository and the target branch is configured.