Installation

System requirements and installation options for CamelMind. Follow this guide to set up and customize your site.

Before you begin, ensure your local machine meets the following requirements:

RequirementMinimum version
Node.js20 or higher
Package managerAny recent version of npm, pnpm, or yarn
Tip

Use nvm or fnm to manage Node versions. Run node --version to check your current version.


Scaffold a new site

Get started in seconds with the CamelMind init CLI. Open your terminal and run the following command, replacing my-docs with your project name.

bash
npx camelmind@latest init my-docs

The CLI will:

  1. Create a new project from the CamelMind starter template.
  2. Install all project dependencies automatically.
  3. Display the next steps to get started.

Next, start the development server:

bash
cd my-docs
npm run dev

Then open http://localhost:3000 in your browser to preview your documentation site.


Manual installation

If you prefer to set up from scratch or integrate CamelMind into an existing Next.js monorepo, install the package directly:

bash
npm install camelmind
Warning

Manual installation is intended for advanced use cases. For most projects, we recommend using the init CLI, which automatically creates your project with the correct directory structure, configuration, and compatible dependency versions.


Update CamelMind

To update an existing CamelMind site, use one of the following update options:

OptionCommand
Update your site to the latest CamelMind platform filesnpx camelmind@latest update
Preview the changes without modifying any filesnpx camelmind@latest update --dry-run
Update files without running npm installnpx camelmind@latest update --no-install
Preserve a customized scaffold file during the updatenpx camelmind@latest update --ignore-file app/page.tsx

Before upgrading, review the changelog for any breaking changes or migration notes.


Environment variables

CamelMind works out of the box with the default configuration. You only need to customize environment variables when enabling features such as authentication or deploying your site to a production domain.

To get started, copy the example file:

bash
cp .env.example .env.local

Then update the values you need.

VariableDefaultDescription
CAMELMIND_URLhttp://localhost:3000The public URL of your documentation site. Update this before deploying (for example, https://docs.example.com).
CAMELMIND_AUTH_ENABLEDfalseEnables built-in authentication.
CAMELMIND_AUTH_REQUIRE_LOGINfalseRequires users to sign in before accessing any page.
SESSION_SECRETA long, random secret used to encrypt user sessions. Required when authentication is enabled.

Deploying to production

Before making your site live, update CAMELMIND_URL to match your production domain. For example:

env
CAMELMIND_URL=https://docs.example.com

Then configure the same environment variables in your hosting provider (such as Vercel, Netlify, or your own infrastructure) before deploying your site.

Tip

If your site is publicly accessible, you can leave authentication disabled. Enable it only if you want to protect your documentation behind a login.

See the Environment Variables reference for the complete list of available options.

July 25, 2026
Was this page helpful?