Mojave supports multiple environments to help you build, test, and deploy with confidence. Each environment has its own base URL and token scope.

We recommend using separate API tokens and databases for each environment to avoid accidental data leakage or billing errors.

Available Environments

🔐 Never use production tokens in staging or local development. Tokens are scoped per environment.

Switching Between Environments

To switch between environments, simply change the base URL and use a token from the corresponding environment.

Example – GET /me in staging:

curl -X GET https://staging-api.mojaveapp.com/v1/me \
  -H "Authorization: Bearer YOUR_STAGING_TOKEN"

Local Environment

You can run Mojave locally using Docker or Node. This is ideal for developers who:

• Want to contribute to Mojave

• Need to build/test internal tooling

• Are self-hosting Mojave for their team

Basic Docker Setup

git clone https://github.com/mojave/mojave
cd mojave
cp .env.example .env
docker-compose up --build

By default, your API will run at:

http://localhost:3000

🧱 You can customize ports, database URLs, and secret tokens in your .env file.

Environment-Specific Behavior

Tips for Managing Environments

• Use separate tokens and users per environment

• Never copy production data into dev or staging without sanitizing it

• Enable feature flags or beta toggles using staging for safe previews

• Use tools like dotenv, direnv, or .envrc to switch configs quickly