nocobase-env-bootstrap（nocobase 环境引导程序） Skills下载安装命令和教程

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：nocobase-env-bootstrap（nocobase 环境引导程序）
来源仓库：https://github.com/nocobase/skills
仓库路径：skills/nocobase-env-bootstrap
安装命令：
npx skills add https://github.com/nocobase/skills --skill nocobase-env-bootstrap
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/nocobase/skills --skill nocobase-env-bootstrap

简介

自动化搭建 NocoBase 项目的开发与测试环境。

适用于新成员快速上手或 CI/CD 流水线初始化。
一键安装依赖、配置数据库和启动服务进程。
需确保系统满足最低硬件和软件要求。nocobase-env-bootstrap 属于运维和基础设施类 Skill，可作为该场景下的辅助能力补充。
生产环境部署前务必修改默认密码和安全设置。

SKILL.md

Goal

Help users set up NocoBase smoothly from zero to running by handling environment checks, installation, local CLI environment bootstrap, application environment management, single-instance upgrade, and high-frequency troubleshooting.

Scope

Detect host environment and required dependencies automatically when possible.
Install and initialize NocoBase with Docker, create-nocobase-app, or Git method.
Start NocoBase in one environment (local machine or single server).
After successful install, automatically bootstrap local nocobase-ctl environment (local) for downstream CLI-first skills.
Provide reusable app environment management actions (add, use, current, list) through skill-local wrapper script for downstream skills.
Run safe single-instance upgrades with explicit pre-check and post-check gates.
Diagnose and fix high-frequency setup and runtime failures.

Non-Goals

Do not handle cross-environment release workflows.
Do not orchestrate migration manager or data promotion between environments.
Do not make irreversible destructive changes (drop database, delete data volumes) without explicit user confirmation.
Do not hide unknown errors; always show the exact command and captured failure signal.
Do not assume built-in external-database compose templates exist; require explicit user-provided DB connection inputs when external DB is needed.

Input Contract

Input	Required	Default	Validation	Clarification Question
`mode`	no	`quick`	one of `quick/standard/rescue`	"Do you want quick mode, standard mode, or rescue mode?"
`task`	yes	inferred from user text	one of `preflight/install/upgrade/diagnose/app-manage`	"Should I run preflight, install, upgrade, diagnose, or app-manage?"
`install_method`	install optional, upgrade optional	install: `docker`; upgrade: `auto`	one of `auto/docker/create-nocobase-app/git`	"Which installation method should be used?"
`release_channel`	install or upgrade	`latest`	one of `latest/beta/alpha`	"Which release channel should be used (`alpha` is recommended when AI build capabilities are needed in docker install)?"
`target_version`	upgrade optional	none	non-empty version or image tag	"Which target version should be upgraded to?"
`backup_confirmed`	upgrade required	`false`	must be `true` before upgrade	"Have you completed and confirmed database backup?"
`upgrade_confirmed`	upgrade required for non-dry-run	`false`	must be `true` before non-dry-run upgrade	"Please confirm the resolved upgrade method/version/restart plan."
`restart_mode`	upgrade optional	`manual`	one of `manual/dev/start/pm2`	"How should app be restarted after upgrade?"
`clean_retry`	upgrade git optional	`false`	boolean (`true/false`)	"If git upgrade fails, should clean-retry be enabled?"
`allow_dirty`	upgrade git optional	`false`	boolean (`true/false`)	"Allow upgrade on dirty git worktree?"
`target_dir`	install/upgrade	current directory	writable path	"Where should the project be created or operated?"
`db_mode`	install	`bundled` for docker; `existing` for create/git	one of `bundled/existing`	"Use bundled database or connect existing database?"
`db_dialect`	install	`postgres`	one of `postgres/mysql/mariadb`	"Use PostgreSQL, MySQL, or MariaDB?"
`db_host`	when `db_mode=existing`	none	non-empty host	"Which DB host should be used?"
`db_port`	when `db_mode=existing`	by dialect (`5432`/`3306`)	numeric port	"Which DB port should be used?"
`db_database`	when `db_mode=existing`	none	non-empty database name	"Which DB database should be used?"
`db_database_mode`	when `db_mode=existing`	`existing`	one of `existing/create`	"Use existing database or create database first?"
`db_user`	when `db_mode=existing`	none	non-empty user	"Which DB user should be used?"
`db_password`	when `db_mode=existing`	none	non-empty password	"Please provide DB password."
`db_underscored`	no	`false`	boolean (`true/false`)	"For local DB, should DB_UNDERSCORED be enabled?"
`port`	no	`13000`	integer 1..65535	"Which app port should be used?"
`network_profile`	no	`online`	one of `online/restricted/offline`	"Can this host access external internet directly?"
`cli_env_name`	no	`local`	non-empty slug	"Which local nocobase-ctl env name should be created?"
`cli_auth_mode`	no	`oauth`	one of `oauth/token`	"Use OAuth mode (default) or token mode for CLI env bootstrap?"
`cli_token_env`	no	`NOCOBASE_API_TOKEN`	valid env variable name	"Which env var stores API token when token mode is used?"
`app_env_action`	only when `task=app-manage`	`current`	one of `add/use/current/list`	"Which app environment action should run: add, use, current, or list?"
`app_env_name`	conditional	none	required for `app_env_action=add/use`	"Which environment name should be used?"
`app_base_url`	conditional	none	required for `app_env_action=add`; valid HTTP/HTTPS URL	"Which application URL should be used for env add?"
`app_scope`	no	`project`	one of `project/global`	"Should this env action use project or global scope?"
`app_token`	conditional	none	required when `app_env_action=add` uses token mode with remote URL	"Please provide API token for token-mode remote environment add."

Default behavior when user says "you decide":

mode=quick
task=install
install_method=docker
release_channel=latest (docker install still runs channel clarification when user did not specify channel)
db_mode=bundled
db_dialect=postgres
db_database_mode=existing
db_underscored=false
port=13000
network_profile=online
cli_env_name=local
cli_auth_mode=oauth
cli_token_env=NOCOBASE_API_TOKEN

Mandatory Clarification Gate

Max clarification rounds: 2
Max questions per round: 3
Never run mutable actions (install/upgrade) until all required inputs for the selected task are resolved.
Docker release-channel clarification gate is mandatory for install:
when task=install and install_method=docker, if user did not explicitly specify release_channel, ask one short question before install:
"Docker default is latest, but current AI build capabilities are more complete in alpha. Install alpha now?"
accepted values: alpha / latest / beta.
if user explicitly indicates stability or production preference, select latest.
record channel decision source as user_explicit, clarified, or default_fallback.
Upgrade gate is mandatory:
backup_confirmed must be true before running upgrade commands.
For upgrade, install_method defaults to auto; resolve method from marker/project files when user does not specify.
upgrade_confirmed must be true before non-dry-run upgrade commands.
If target_version is lower than current version, stop (downgrade is not supported).
For install_method=git, block dirty worktree unless allow_dirty=true.
For task=app-manage:
If app_env_action=add, require app_env_name and app_base_url.
DB policy is mandatory for install:
docker default is db_mode=bundled.
If user provides DB connection inputs on docker path, switch to db_mode=existing.
create-nocobase-app and git always require db_mode=existing plus PostgreSQL/MySQL/MariaDB readiness.
for db_mode=existing, require db_database_mode decision:
existing: connect and verify existing database directly.
create: create database first, then connect/verify to avoid repeated initial connection failures.
If DB host is local (localhost, 127.0.0.1, ::1, host.docker.internal), ask for db_underscored preference; default to false when user does not specify.
If DB is missing or unreachable for existing mode, stop and provide official install links:
PostgreSQL: https://www.postgresql.org/download/
MySQL install docs: https://dev.mysql.com/doc/en/installing.html
MySQL downloads: https://dev.mysql.com/downloads/mysql
MariaDB downloads: https://mariadb.org/download/
App env auth-mode rule is mandatory:
default add mode is oauth (unless token args are provided without explicit auth-mode).
oauth mode requires dependency bundle @nocobase/plugin-api-doc + @nocobase/plugin-idp-oauth and interactive env auth.
token mode local URL (strict): host in localhost, 127.0.0.1, ::1, *.localhost, or host.docker.internal -> token is mandatory but auto-acquired by env-manage (never use placeholder token).
token mode remote URL: token must be manually provided by user (app_token or token env).
For install flows, always run CLI environment bootstrap (node./scripts/env-manage.mjs add...) as final stage.
Before running env update, ensure CLI dependency plugins are active by auth mode:
oauth: @nocobase/plugin-api-doc + @nocobase/plugin-idp-oauth
token: @nocobase/plugin-api-doc + @nocobase/plugin-api-keys
If token mode is used and cli_token_env is missing during CLI bootstrap, attempt automatic token generation first; ask user manually only when automatic path fails.
If required inputs are missing or ambiguous, stop and ask one short clarification question.
If any required path is invalid or not writable, stop and request a valid writable path before continuing.

Workflow

Parse request and normalize intent.

If intent is unclear, ask only one short question to select task.
Keep first round to at most five questions.
For docker install, resolve release_channel with this priority:
user explicit input > docker channel clarification answer > default fallback latest.

Run preflight gate before install/upgrade.

For install/upgrade, run core checks only:
Windows: execute powershell -File scripts/preflight.ps1 -InstallMethod <install_method> -DbMode <db_mode> -DbDialect <db_dialect> -DbHost <db_host> -DbPort <db_port> -DbDatabase <db_database> -DbDatabaseMode <db_database_mode> -DbUser <db_user> -DbPassword <db_password>.
Linux/macOS: execute bash scripts/preflight.sh <port> <install_method> <db_mode> <db_dialect> <db_database_mode> with DB_HOST/DB_PORT/DB_DATABASE/DB_USER/DB_PASSWORD in environment.
Classify findings into fail, warn, and pass.
Treat dependency/runtime/path/network blockers as immediate blockers.

Execute by mode.

quick: Docker-first path with minimal questions.
quick + docker install: if user did not provide channel, ask the mandatory docker channel clarification and recommend alpha.
standard: user chooses method and database dialect.
rescue: collect diagnostics (powershell -File scripts/collect-diagnostics.ps1 on Windows, bash scripts/collect-diagnostics.sh on Linux/macOS), map findings to troubleshooting entries, then apply the smallest safe fix first.
Install execution policy:
Use local scripts and templates only.
Docker path uses assets/docker-templates/.
create-app/git path uses assets/install-templates/.
Do not search web pages for install command snippets during execution.

Execute task-specific runbook.

For install: follow Install Runbook.
For install command execution, use local script:
Windows: powershell -File scripts/install.ps1 --method <install_method> --target-dir <target_dir> --release-channel <release_channel> --db-mode <db_mode> --db-dialect <db_dialect> --db-host <db_host> --db-port <db_port> --db-database <db_database> --db-database-mode <db_database_mode> --db-user <db_user> --db-password <db_password> --db-underscored <db_underscored> --project-name <project_name>
Linux/macOS: bash scripts/install.sh --method <install_method> --target-dir <target_dir> --release-channel <release_channel> --db-mode <db_mode> --db-dialect <db_dialect> --db-host <db_host> --db-port <db_port> --db-database <db_database> --db-database-mode <db_database_mode> --db-user <db_user> --db-password <db_password> --db-underscored <db_underscored> --project-name <project_name>
For upgrade: follow Upgrade Runbook and execute local script:
Windows: powershell -File scripts/upgrade.ps1 --method <install_method|auto> --target-dir <target_dir> --backup-confirmed true --confirm-upgrade true --target-version <target_version> --restart-mode <restart_mode> --clean-retry <clean_retry> --allow-dirty <allow_dirty>
Linux/macOS: bash scripts/upgrade.sh --method <install_method|auto> --target-dir <target_dir> --backup-confirmed true --confirm-upgrade true --target-version <target_version> --restart-mode <restart_mode> --clean-retry <clean_retry> --allow-dirty <allow_dirty>
For diagnose: follow Troubleshooting KB.
For app environment management (task=app-manage): follow App Environment Manage.

Run post-check gate and bootstrap CLI environment.

Verify service availability, login path, basic plugin/runtime health, and error logs.
For install, app startup and login readiness complete core install flow.
Ensure CLI dependency plugin bundle is active before CLI runtime refresh:
oauth (default): @nocobase/plugin-api-doc + @nocobase/plugin-idp-oauth
token: @nocobase/plugin-api-doc + @nocobase/plugin-api-keys
Preferred activation path:
oauth: Use $nocobase-plugin-manage enable @nocobase/plugin-api-doc @nocobase/plugin-idp-oauth
token: Use $nocobase-plugin-manage enable @nocobase/plugin-api-doc @nocobase/plugin-api-keys
If plugin state changed, restart app before node./scripts/run-ctl.mjs -- env update....
Always run CLI bootstrap as final stage for install/upgrade:
Windows: powershell -File scripts/cli-postcheck.ps1 -Port <port> -EnvName <cli_env_name> -AuthMode <cli_auth_mode> -TokenEnv <cli_token_env> -Scope project -BaseDir <target_dir>
Linux/macOS: AUTH_MODE=<cli_auth_mode> bash scripts/cli-postcheck.sh <port> <cli_env_name> <cli_token_env> project <target_dir>
CLI bootstrap target command:
node./scripts/env-manage.mjs add --name <cli_env_name> --url http://localhost:<port>/api --auth-mode <cli_auth_mode> --scope project --base-dir <target_dir>
After env add succeeds, run runtime refresh for downstream command readiness:
node./scripts/run-ctl.mjs -- env update -e <cli_env_name> -s project
Perform immediate readback (node./scripts/env-manage.mjs current --scope project --base-dir <target_dir>) and include expected vs actual values.

Report output.

Include command list executed.
Include evidence of success/failure from command output.
Include release_channel_source evidence (user_explicit/clarified/default_fallback) for install flows.
For every write action (for example .env, compose file, or runtime config), perform immediate read-after-write verification and report expected vs actual values.
Include CLI bootstrap evidence:
cli_env_name
base_url
scope
auth_mode
env_update_status
For task=app-manage, include app env operation evidence:
app_env_action
current_env_name
current_base_url
is_local
auth_mode (for add)
token_mode (for add)
For install success paths, include first-login credentials:
if root credentials were not explicitly customized, show default admin@nocobase.com / admin123 and remind user to rotate password.
if customized, show configured login account and password source.
Include one clear next action.

Reference Loading Map

Reference	Use When	Notes
assets/docker-templates.md	docker install	local template selector and release-channel mapping
assets/install-templates.md	create-app/git install	local command/env template mapping and channel defaults
references/preflight-checklist.md	before install/upgrade	dependency, path, network, and port checks
references/install-runbook.md	install and first startup	docker/create-app/git execution guide
references/app-env-manage.md	`task=app-manage`	add/use/current/list contract with oauth/token auth-mode policy
references/upgrade-runbook.md	single-instance upgrade	pre-check, execution, post-check, rollback guidance
references/troubleshooting.md	diagnose and recovery	high-frequency issue decision table

Safety Gate

High-impact actions:

modifying running service version
changing runtime environment variables
restarting production-like services
replacing or removing compose services

Safety rules:

Require explicit confirmation before any upgrade action.
Require backup confirmation before upgrade.
Require --confirm-upgrade true before non-dry-run upgrade script execution.
Never run destructive delete commands automatically.
If commands fail, stop and surface exact failure output before next action.

Confirmation template:

"Confirm execution: {{task}} on {{target}} with method {{install_method}}. Impact: runtime may restart and service may be briefly unavailable. Reply confirm to continue."

Verification Checklist

Preflight completed and contains zero unresolved blocking failures.
Preflight fails when APP_KEY is weak for existing project files, and defers missing APP_KEY only for fresh install targets before local install script generation.
Docker install without explicit channel triggers clarification and recommends alpha.
Explicit user channel choice is respected without re-asking.
Existing DB mode fails when required DB fields are missing or endpoint is unreachable.
create-nocobase-app/git fail preflight when PostgreSQL/MySQL/MariaDB is unavailable.
Method and release channel are explicitly confirmed or defaulted.
Install commands are recorded and reproducible.
Install core success is determined by app startup and login readiness.
CLI final stage runs for install/upgrade and successfully creates/updates local env via skill-local env helper (node./scripts/env-manage.mjs add...).
task=app-manage supports add/use/current/list through node./scripts/env-manage.mjs....
App env add enforces auth-mode rules correctly (oauth default with metadata/auth flow; token mode keeps local-vs-remote token policy).
App env add is not considered success unless env update connectivity verification succeeds.
CLI runtime refresh (node./scripts/run-ctl.mjs -- env update...) succeeds for the bootstrap env.
If runtime refresh fails with swagger:get 404 or API documentation disabled, skill applies plugin activation sequence and retries.
OAuth path confirms @nocobase/plugin-idp-oauth is active before OAuth metadata/auth verification.
Token acquisition path confirms @nocobase/plugin-api-keys is active before generating/providing token.
Readback confirms expected env name/base URL/scope and current env selection.
Upgrade path includes backup confirmation.
Upgrade path includes script-level confirmation gate (--confirm-upgrade true) after plan readback.
Post-check verifies app reachability and login page.
Troubleshooting output includes root-cause hypothesis and concrete fix steps.
Result summary contains completed, pending, and next action items.
Every write action includes immediate readback evidence.

Minimal Test Scenarios

Quick install on a clean host with Docker available, then CLI local env bootstrap runs automatically.
Preflight with missing Docker and missing Node.
Preflight fails on missing or placeholder-like APP_KEY, and passes after random key is set.
Install preflight blocks on critical issues.
CLI bootstrap default oauth path fails when idp-oauth is missing, then succeeds after dependency auto-enable/login fix.
CLI bootstrap token mode fails when token is missing, then succeeds after auto-generate/manual token fix.
Upgrade with method auto-detected, backup confirmed, upgrade plan confirmed, and successful post-check.
Diagnose Environment mismatch and produce actionable steps.
Diagnose startup failure caused by port conflict and provide fix command.
Diagnose startup failure caused by file permission denied (EACCES) and provide concrete permission/access fix steps.
Docker install in offline mode succeeds using local compose template without external docs lookup.
Docker install with user-provided DB inputs auto-switches to db_mode=existing.
create/git preflight fails when DB is unavailable and returns official PostgreSQL/MySQL/MariaDB install links.
create/git preflight passes when DB endpoint and auth probe succeed.
task=app-manage with oauth mode validates metadata/auth flow, runs env update, and returns current env info only on full connectivity success.
task=app-manage with token mode remote URL + missing token fails with clear token-required error.
Docker install without explicit channel asks clarification and records release_channel_source=clarified when user chooses.
Docker install with explicit channel keeps user choice and records release_channel_source=user_explicit.

Output Contract

Final response must include:

selected mode and task
inputs used (method, channel, directory, port)
release_channel_source (user_explicit/clarified/default_fallback)
preflight summary (fail/warn/pass)
actions executed
verification result
CLI bootstrap result (cli_env_name, base_url, scope, env_update_status)
unresolved risks
recommended next action

For install tasks, recommended next action must include:

login URL
first-login account and password
password rotation reminder

References

Usage Guide: human-readable guide for install, CLI bootstrap, app environment management, upgrade, and diagnose workflows.
Docker Templates: local-first compose template selector and release-channel mapping.
Install Templates: local command templates for create-app/git plus channel mapping overrides.
Preflight Checklist: use before any mutable action.
Install Runbook: use for install and startup flows.
App Environment Manage: use for app env add/use/current/list operations and oauth/token policy.
Upgrade Runbook: use for safe single-instance upgrades.
Troubleshooting KB: use for high-frequency failures.
NocoBase Docker Installation: primary Docker install reference. [verified: 2026-04-08]
NocoBase Docker Upgrading: Docker upgrade constraints and sequence. [verified: 2026-04-08]
NocoBase create-nocobase-app Installation: create-app bootstrap path. [verified: 2026-04-08]
NocoBase Git Installation: source-code install path. [verified: 2026-04-08]
NocoBase Environment Variables: runtime env configuration references. [verified: 2026-04-08]
Docker Install Docs: Docker setup guidance for missing dependency. [verified: 2026-04-08]
Node.js Downloads: Node.js installation reference. [verified: 2026-04-08]
Git Install: Git installation reference. [verified: 2026-04-08]
Yarn Classic Install: Yarn 1.x installation reference. [verified: 2026-04-08]
PostgreSQL Download: PostgreSQL installation guide and packages. [verified: 2026-04-15]
MySQL Install Docs: MySQL official installation documentation. [verified: 2026-04-15]
MySQL Downloads: MySQL official download page. [verified: 2026-04-15]
MariaDB Downloads: MariaDB official download page. [verified: 2026-04-16]

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.18%

按下载量换算207

Claude

32.55%

按下载量换算191

Cursor

17.54%

按下载量换算103

Gemini CLI

8.83%

按下载量换算52

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置，应进入高风险复核队列，默认不自动发布。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果，不能写成本站确认安全。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/nocobase/skills

SKILL.md 来源

github.com

/nocobase/skills/tree/main/skills/nocobase-env-bootstrap

skills-sh

skills.sh

/nocobase/skills/nocobase-env-bootstrap

继续浏览同类 Skills

更多运维和基础设施 Skills（2,449）返回 Skills 目录

上一个 Skill

nix（尼克斯）

nix 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

nocobase-install-start（nocobase 安装开始）

nocobase-install-start 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。