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"

Projects & Git

Creating a project Connecting GitHub Connecting GitLab Branches and instances

Instances & Console

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

Monitoring & Backups

Monitoring your instance Backups and restore Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource

Account & Security

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

Billing & Plans

"Plans: Free, Pro and Enterprise" Upgrading and managing your subscription What happens when you hit a plan limit

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

"Troubleshooting: cannot connect a server" "Troubleshooting: a deployment failed" "Troubleshooting: my instance is down or slow" "Troubleshooting: domain or SSL problems"

Concepts

Production, staging and development stages

What stages are in CICDoo, how servers are assigned per stage when creating a project, and how instances are grouped by stage in the console.

What stages are

Every instance in CICDoo belongs to one of three stages:

  • Production: your live environment that real users depend on.
  • Staging: a place to test changes in conditions close to production.
  • Development: environments for building and trying out new work.

Stages let you keep experimental branches safely separated from the environment your business runs on, while managing everything from one project.

Assigning servers per stage

You choose which server hosts each stage when you create a project. In the last step of the Create New Project wizard (Servers), the Server Assignment section has three fields:

  • Production Server: required. Every project needs at least one server, and it is the production one.
  • Staging Server: optional.
  • Development Server: optional.

For each field, click into the search box, type to filter your servers by name, hostname or IP, and select one. You can clear a selection with the X on the selected server card. If you have no servers yet, the wizard points you to the Servers page to add one first, see Adding a server.

A small setup can point all stages at the same server, while larger setups typically give production its own machine.

Stages in the project console

Open a project's console and the left sidebar lists its instances grouped by stage, each with a colored dot:

  • Production (green)
  • Staging (amber)
  • Development (blue)

Click an instance (shown by its branch name) to open it. Next to the Staging and Development headings there is a plus button to create a new instance in that stage: enter a branch name, choose the base branch to fork from, and click Create. The stage is filled in automatically from the section you clicked.

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

Previous What happens when you hit a plan limit Next Domains, subdomains and SSL

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