Definições

The Settings view allow you to manage the configuration of your project.

Nome do projeto

The name of your project defines the address used to access your production database. The addresses of your staging and development builds are automatically derived from this name. If you change the project name, only future builds will use the new name.

Colaboradores

To grant access to a GitHub user, enter their username and click Add. By default, the user is is granted the Developer role. Click the dropdown menu to select another one:

• Admin: full access to all Odoo.sh features and tools. This role is dedicated to project management and has exclusive access to the project’s settings.

• Tester: access to staging and development databases and their tools. This role is intended for users performing user acceptance testing (UAT). Testers can work with copies of production data, but they cannot access the production database through Odoo.sh’s tools.

• Developer: no access to the production and staging databases. This role is intended for users who modify the code but should not access production data. Developers cannot connect to the production or staging databases and do not have access to the web shell or server logs.

Feature access by stage and role

Estágio	Feature	Desenvolvedor	Verificador	Admin
Desenvolvimento	Connect + / Connect as	●	●	●
	History	●	●	●
	Mails	●	●	●
	Editor	●	●	●
	Monitor	●	●	●
	Logs	●	●	●
	Upgrade	●	●	●
	Settings	●	●	●
	Status	●	●	●
Teste	Connect + / Connect as	●	●	●
	History	●	●	●
	Mails	●	●	●
	Shell	●	●	●
	Editor	●	●	●
	Monitor	●	●	●
	Logs	●	●	●
	Upgrade	●	●	●
	Settings	●	●	●
	Status	●	●	●
Produção	Connect + / Connect as	●	●	●
	History	●	●	●
	Shell	●	●	●
	Editor	●	●	●
	Monitor	●	●	●
	Logs	●	●	●
	Backups	●	●	●
	Upgrade	●	●	●
	Settings	●	●	●
	Status	●	●	●

Legenda

● : Available

● : Not available

Nota

• Only admins can access the audit logs and the project settings.

• All roles can access the builds page, but the features available are specific to each role.

Public access

When enabling Allow public access, the builds page becomes publicly accessible, allowing visitors to connect to development builds. Visitors can also access logs, the shell, and mails for development builds. Production and staging builds remain private; visitors can only view their status.

Status dos commits do GitHub

You can add a GitHub token to allow Odoo.sh to push commit statuses back to GitHub. The token must have the commit statuses (write) repository permission.

Veja também

For more information, refer to GitHub’s documentation on managing access tokens.

GitHub key and webhook

A deploy key and a webhook are automatically created on your GitHub repository to allow Odoo.sh to fetch code and receive commit notifications. As they can be unintentionally modified or deleted, you can use the Verify Deploy Key and Verify Webhook buttons below to verify their configuration.

Nota

Administrative rights on the GitHub repository are necessary.

Submódulos

The git submodule command allows you to integrate other Git projects into your codebase without copying the code directly.

Nota

A Git repository containing Odoo modules, for example from the Odoo Apps Store or community modules, is necessary.

Private repositories

Before adding private GitHub repository as a submodule, it is necessary to add a deploy key:

1. Paste the SSH URL of the sub-repository (e.g., git@github.com:USERNAME/REPOSITORY.git) and click Add.

2. Copy the generated Public Key.

3. On the sub-repository’s GitHub, go to Settings ‣ Deploy keys.

4. Click Add deploy key, enter a Title, paste the public key into the Key field, and click Add key.

To add a public repository or private repository with a deploy key as a submodule:

1. Add the submodule to your project.

   git submodule add -b BRANCH git@github.com:USERNAME/REPOSITORY.git PATH
   

2. Commit and push the change.

   git commit -a && git push -u origin master
   

3. Wait for Odoo.sh to rebuild the project.

Production database size

This section displays the total storage used by the project. It includes the PostgreSQL database size and disk files in your container (database filestore, session storage, etc.). If the production database exceeds the storage included in your subscription, the plan will be automatically adjusted.

Dica

To analyze disk usage, run the Ncdu tool in the web shell.

Database workers

Additional database workers can be configured to allow your production database to handle higher concurrent loads.

To add more workers, contact your account manager. After payment, the new worker(s) will be added to your project.

Nota

Adding more workers does not automatically fix performance issues. It only increases the number of concurrent connections the server can handle. If some operations remain slow, the issue is likely code-related. If it is not due to your customizations, contact Odoo Support.

Staging branches

Additional staging branches allow you to develop and test multiple features simultaneously. To add more staging branches, request a product increase directly from your Odoo.sh project. A widget will guide you to the subscription portal to complete the purchase. After payment, synchronization with Odoo.sh will occur automatically, and the number of available staging branches will be updated.

Ativação

This section shows the activation status of the project. You can change the activation code if necessary, provided the new code is not already assigned to another project.

Aviso

You cannot change the activation code to:

• A code already used in another project

• A trial code (downgrading from paid to trial is not allowed)

• An invalid code (not linked to an Odoo.sh custom plan)

For any other issue, contact Odoo Support.