All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Concepts

Odoo versions and editions (Community vs Enterprise)

How to choose the Odoo version and edition when creating a project, and how to set up the GitHub classic token that Enterprise edition requires.

Choosing an Odoo version

When you create a project, the Version field sets which Odoo version the project runs. You can pick any major version from 11.0 upward, including the most recent releases and their intermediate versions, as well as master (the in-development branch). Production always runs the project version. Staging and development instances default to it too, but you can pick another version for an individual instance to test an upgrade.

Community vs Enterprise

The Edition field offers two choices:

  • Community (Open Source): the default. Odoo Community is open source and needs no special access.
  • Enterprise (Requires a classic token): Odoo's commercial edition. Its source code lives in private repositories owned by Odoo, so extra requirements apply (see below).

What Enterprise edition requires

Enterprise needs a GitHub classic token from a GitHub account that has access to the Odoo Enterprise repositories. Because those repositories are private, Odoo has to grant your GitHub account access first, typically through an Odoo Enterprise subscription or partnership. Connecting GitHub with the "Connect with GitHub" sign-in alone is not enough: the project form only lets you continue with Enterprise once a classic token is saved.

Set up a GitHub classic token

You can add the token from the project form or from Settings.

  1. At GitHub, create a classic token with the repo and read:user scopes, signed in as the account that has Odoo Enterprise access. The form's "GitHub Settings" link opens the right GitHub page with those scopes selected.
  2. In CICDoo, open Settings, go to the Integrations tab, and in the "Enterprise Edition Requires a Classic Token" box click "Configure a classic token". Alternatively, in the "Create New Project" form, choose Enterprise and click "Configure a classic token" in the notice that appears; the form jumps back to the Source step to show the token field.
  3. Paste the token into "GitHub Classic Token".
  4. Click "Save token".

When the token is saved, the Enterprise notice in the project form shows "Classic token configured - ready for Enterprise".

Create a project with a version and edition

  1. Open Projects and click "Add Project" (or use the onboarding wizard).
  2. On the Source step, connect your Git provider (GitHub or GitLab) if you have not already, choose "New Project" or "Existing Project", and click "Next".
  3. On the Details step, enter the "Project Name" (and a repository name for a new project).
  4. Pick the Version.
  5. Pick the Edition. If you choose Enterprise, the "Enterprise Edition Requires a Classic Token" notice appears. If it shows "Configure a classic token", set up the token as described above, then return to the Details step with "Next".
  6. Click "Next", assign at least a production server, see Production, staging and development stages, then click "Create Project".

Related: Creating a project, Connecting GitHub, Profile and integrations settings.

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

Previous Domains, subdomains and SSL Next Workspaces and team collaboration

Still stuck? Open a ticket from the app or talk to an engineer.