NocoBase CLI Overview
If this is your first time using this CLI, you don’t need to memorize all the commands at the beginning. Use nb init --ui to install an application first, and then continue looking at the rest according to the scenario.
First establish the most important mind
In NocoBase CLI, subsequent operations do not revolve around "a certain directory" or "a certain port" by default, but around env.
You can think of env as "a set of application connection and running information remembered by the CLI". As long as it has been saved successfully, many subsequent commands can be used directly:
- Use
nb initto install a new application and save it as env - Use
nb env addto connect an existing application to the CLI - Manage this env with
nb app start,nb app logs,nb app upgrade - Backup and restore this env using
nb backup - Use
nb app autostart,nb proxyto continue to supplement the production environment capabilities
Keep this in mind first, and the subsequent documents will be much smoother.
Default recommended path
If you're not sure where to start, it's usually easiest to follow this path:
- First read Install using CLI and complete
nb initonce. - After the application is saved as env, look at Multiple Environment Management to confirm the current env, switch env, and check the status.
- For daily startup, stop, log and upgrade, continue to see Manage Application.
- Before making upgrades, migrations or important changes, see Backup and Restore.
- If you are ready to officially go online, then enter [Production Environment Deployment Overview] (./production/index.md).
The first three steps cover most usage scenarios.
Quick index
When to look at the command reference
This set of quick start documents is more about "what do I want to do now". If you already know which command you want to run and only want the full parameters, go straight to NocoBase CLI Command Reference.
The default suggestions are:
- First use this overview and the quick start documents to establish a sense of path
- Then check the parameter details on the specific command page
This makes it easier to get started than reading the complete command tree at first glance.

