Project environments, extensions and deletion

Opening the project settings

You need permission to change the project's settings ("Project settings").

1. On the Projects page, click "Settings" on the project's card. From the project console, you can also use the "Project Settings" link at the bottom of the sidebar.
2. The "Project Settings" page opens on the "General" tab.

The page has these tabs: "General", "GitHub", "Environments", "Storage", "Notifications", "Agent", "Advanced" and "Subscription". Changes on any tab are kept only when you click "Save Changes" at the top right. The "Console" button next to it takes you back to the project console.

This article covers "General", "Environments" and "Advanced". For the other tabs, see Project GitHub settings and webhook, S3 storage, uploads and bulk backup actions, Alert notifications (email and SMS), Setting up agent tasks and Upgrading and managing your subscription.

Renaming a project

1. On the "General" tab, change "Project name".
2. Click "Save Changes".

The name is a label shown across CICDoo. Renaming does not change the Git repository. The "Project UUID" below it is a fixed identifier you can copy, for example when you contact support.

Changing the Odoo version or edition

1. On the "General" tab, pick a new "Odoo Version".
2. Pick the "Edition": "Community Edition" or "Enterprise Edition". Enterprise needs a GitHub classic token with access to the Odoo Enterprise repositories, see Odoo versions and editions (Community vs Enterprise).
3. Click "Save Changes".

The version applies to every instance of the project except those pinned to their own version when they were created. Changing the version does not migrate an existing database. To try a new version safely, create a staging or development instance with a different "Odoo Version" first, see Creating an instance.

Pinning Odoo to specific commits (Time Machine)

Time Machine runs your instances on a fixed commit of the Odoo source instead of the latest code. Use it when a recent Odoo change breaks your custom code.

1. On the "General" tab, turn on the "Time Machine" switch.
2. Enter the "Community Commit Hash" and the "Themes Commit Hash".
3. On an Enterprise project, also enter the "Enterprise Commit Hash".
4. Click "Save Changes".

All the shown hash fields are required while Time Machine is on. To return to the latest code, turn the switch off and save.

Assigning servers to each stage

The "Environments" tab has one card per stage: "Production Environment", "Staging Environment" and "Development Environment". Each card shows the current server under "Current:", or "Not configured". A "DNS Validated" badge appears on a card once the domain setup for that stage has been confirmed.

1. Open the "Environments" tab.
2. In "Production Server", "Staging Server" or "Development Server", type to search and pick a server.
3. Click "Save Changes".

Setting a staging or development server is what lets you create instances in that stage from the console. See Branches and instances.

Moving a stage to another server

Picking a different server for a stage that already has instances moves those instances to the new server. Their address is updated for the new server.

Note: The Odoo database and files are not copied to the new server, and the copy left on the old server is removed automatically, including its database, filestore and the backups stored on that server. Take a backup first and keep it in S3 so you can restore it on the new server. See Backups and restore.

1. Take a backup of each instance you want to keep and make sure it is uploaded to S3.
2. On the "Environments" tab, pick the new server for the stage.
3. Click "Save Changes".
4. When the instance is running on the new server, restore the backup into it.

Installing IDE extensions

The Web IDE of every instance can install extensions for you when it starts.

1. Open the "Advanced" tab.
2. In "IDE Extensions", enter one extension identifier per line, for example ms-python.python.
3. Click "Save Changes".

Extensions are installed the next time each instance starts. An extension that cannot be found or times out is skipped. See Web IDE and remote access.

Adding extra repositories

Extra repositories are other Git repositories, for example shared modules, cloned next to your project's code in every instance.

1. Open the "Advanced" tab.
2. In "Extra Repositories", enter one repository per line in the form URL,branch,commit, for example https://github.com/owner/repo.git,18.0,abc1234. The commit can also be a tag, or left out to use the latest tag. Lines starting with # are ignored.
3. Click "Save Changes".

The URL must be a GitHub address. Each line is checked when you save, and a line with a wrong URL, branch or commit is refused with a message. Restart the instances to pick up the change. A single instance can replace this list with its own, see Instance settings explained.

Deleting a project

Deleting a project destroys its running instances. On every server the project runs on, the Odoo database, the filestore and the backups stored on that server are destroyed. Backups already uploaded to your own S3 bucket are kept. The project then disappears from the Projects page.

Note: You do not need to delete a project because it became read-only after a missed payment. An unpaid subscription never destroys anything, and paying restores the project. See If a project subscription goes unpaid.

You need the "Delete projects" permission.

1. If you want to keep the data, make sure a recent backup of each instance is in your S3 bucket.
2. Open the project settings and go to the "Advanced" tab.
3. In the "Danger Zone" card, click "Delete Project".
4. Read the warning and confirm.
5. Wait for "Project deleted successfully!". You are taken back to the Projects page.

The project record is kept hidden on the platform rather than erased, but its instances and their data on the servers cannot be recovered.

Related: Creating a project, Production, staging and development stages, Tagging and filtering projects, High availability with app nodes, Deleting a server.

If you get stuck, open a support ticket from the Tickets page or the chat widget.