All articles
Getting Started
What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure MapConcepts
Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaborationServers
Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and chartsProjects & Git
Creating a project Connecting GitHub Connecting GitLab Branches and instancesInstances & 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 queueAgent Tasks
What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-upsMonitoring & 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 resourceAccount & Security
Two-factor authentication (2FA) Profile and integrations settings Passwords and account recoveryBilling & Plans
Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner programSupport & Tickets
Opening a support ticket Getting help from the CICDoo teamTroubleshooting
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 problemsGetting Started
Getting started: the onboarding wizard
How the onboarding wizard works, including the solo and team paths, the guided first server and project, and cloud credit offers.
Choosing how you will use CICDoo
When you first sign in, the onboarding wizard asks "How will you use CICDoo?" and offers two paths:
- Just me: deploy and manage your own servers and projects.
- With my team: share a workspace, invite members, and manage access together.
This choice only tailors your setup. You can still invite teammates later. If you were invited to someone else's workspace, those workspaces are listed at the top so you can jump straight in.
The team path
Team plans are quoted rather than picked from a list, so this step does not open a checkout. Instead the wizard invites you to send a request: there is a box for anything we should know, such as your team size and how many projects and servers you expect, and a "Request a team plan" button. Our team gets back to you, usually within one business day, and sets the account up. Once your plan is active, you name your workspace and pick a URL slug, then continue. You are never stuck waiting: "Continue solo in the meantime" switches you to the solo path, and you can move to a team workspace later.
Your first server and project
The final step is a short checklist to get your first deployment running:
- Add your first server: connect a machine (host or IP plus SSH) for CICDoo to deploy to. See Adding a server.
- Create a project: point it at your repository.
The "Go to dashboard" button unlocks once you have both a server and a project.
No server yet?
If you have not added a server, the wizard shows free credit offers from cloud providers where you can spin one up: Google Cloud, AWS, OVHcloud, Vultr and Linode (Akamai). These are third party offers, and the exact credit and eligibility terms apply on each provider's site.
If you would rather not deal with servers at all, use the "Schedule a meeting" button in the same section to book a quick call, and the CICDoo team can host and manage everything for you.
If you get stuck, open a support ticket from the Tickets page or the chat widget.
Still stuck? Open a ticket from the app or talk to an engineer.