Command-line guide
The Cloud Noce CLI handles tasks normally performed in the dashboard: signing in, viewing projects and services, deploying a local folder directly, managing environment variables, connecting domains, viewing builds and releases, rolling back to previous versions, reading logs and controlling PaaS services. It is useful for projects that are not connected to GitHub or GitLab, or when deploying from CI/CD, internal scripts or a local terminal. The CLI uses only the public Cloud Noce API and stores its sign-in token in your user configuration.
Important considerations
Recommended one-command installation
Run curl -fsSL https://get.gerdoo.cloud/install.sh | sh. The installer detects your operating system and architecture, downloads the correct binary and places it in /usr/local/bin. If that directory is not writable, it uses sudo only to move the file.
Tokens and configuration storage
After gerdoo login, the CLI token is stored in ~/.config/gerdoo/config.json with permissions 0600. In CI, use GERDOO_TOKEN instead of login to avoid writing the token to disk.
Deploying a local folder
During deploy, the project folder is packaged as tar.gz and uploaded. The .git, node_modules and .gerdoo directories and .DS_Store files are always excluded. Create .gerdooignore to exclude additional paths.
Getting started with the CLI
Install the CLI
Run curl -fsSL https://get.gerdoo.cloud/install.sh | sh, or download the appropriate binary manually and place it on PATH.
Sign in
Run gerdoo login and sign in to your Cloud Noce account with your email or mobile number and password. Then run gerdoo whoami to check the account.
Deploy your first service
In the project root, run gerdoo deploy. The CLI creates the service automatically and asks for confirmation once; --yes skips confirmation. After success, .gerdoo/service.json links the project to the created service.
Set variables and redeploy
If the project needs variables such as DATABASE_URL or SECRET_KEY, set them with gerdoo service env <slug> set KEY=VALUE, then run gerdoo deploy again.
Monitor and troubleshoot
Read service logs with gerdoo logs <slug> --tail 200 or gerdoo service logs <slug>, and check status with gerdoo service status <slug>.
Connecting an AI assistant (MCP and agents)
The Cloud Noce CLI also includes an MCP server. Connect assistants such as Claude Code, Cursor, Codex or Gemini Antigravity to your Cloud Noce projects with one command: gerdoo setup agent. See MCP and agent setup for complete details.