Configuration

This page is the configuration reference of a self-hosted Nodaro: every environment variable that operators set, grouped by purpose, with its default. On the bundled compose stack, every variable has a working default, so you set only what you want to change. Variables that apply only to Nodaro Cloud are not listed.

How to set a variable

On the compose stack, you set a variable in one of two places:

• In .env, next to docker-compose.community.yml. This works for the variables that the compose file passes to the app. The tables below say Yes in the .env column for them.
• In the compose file, for every other variable. Add it under environment: of the nodaro service:

  nodaro:
    environment:
      # ...the variables already listed...
      MCP_ENABLED: "true"
      MCP_PUBLIC_URL: https://mcp.nodaro.example.com

Then apply the change:

docker compose -f docker-compose.community.yml up -d

Nodaro reads its environment at boot. The only exception is the provider keys you paste on /setup, which apply at once. Outside the compose stack, set the variables in your platform's environment settings.

Required outside the compose stack: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY and INTERNAL_ORCHESTRATOR_SECRET. Without them, the API refuses to start and lists the missing or invalid variables.

Instance

Secrets

Generate a secret with openssl rand -hex 32. Back up the encryption key with the database: see Backups and restore.

Database and sign-in

Queues

Storage

Model providers

Each of these keys can also be pasted on /setup. A key set in the environment wins. See Provider keys.

Nodaro Cloud connection

NODARO_API_KEY and R2_SHARED_WITH_RELAY_TARGET also belong to the connection. See Connect to Nodaro Cloud.

Workers and performance

Read Scaling before you raise these.

Editors

See Video and audio editors.

Updates

See Updating.

MCP

See MCP.

Sign-in and roles

See Single sign-on and First user and admin.

Integrations

For the Figma plugin, register a developer app on your install with <PUBLIC_URL>/v1/oauth/plugin/callback as a redirect URI and the scopes jobs:read, assets:read, assets:write and credits:read. Then set its client ID here. When the variable is empty, the plugin connection routes answer 503 and nothing else changes. See OAuth apps.

Build-time settings

These are fixed when the image is built. Change them in the compose file's build: args: and rebuild.

Video and audio editors

Edit in NodarCut on a video result on the canvas, and Edit on a video result in an app, open the NodarCut video editor. Edit on an audio result in an app opens the AudioMass editor. Your media does not go to the editor's server: the app reads the file from your own storage and hands it to the editor inside the browser. The editing and the export happen there.

• Video. With FREECUT_URL empty, the editor loads from freecut.nodaro.ai, which allows embedding only from http://localhost:3000. On another origin, such as a LAN address or a domain, the browser refuses it and the panel explains why. Open an issue on GitHub with the URL you serve to have it allowed, or run your own FreeCut. FreeCut is public, MIT-licensed and ships a Dockerfile. Then set FREECUT_URL=https://freecut.example.internal.
• Audio. There is no public hosted AudioMass, so until you configure it, Edit on an audio result opens no editor. On the Present tab it does nothing, and outside the editor it shows a panel that explains what to set. Run Nodaro's fork, AudioMass, which supports the in-browser handoff that the original AudioMass lacks. Then set AUDIOMASS_URL=https://audiomass.example.internal.

Restart the stack after a change. No rebuild is needed.

Model maker logos

GET /v1/models names the maker of each model and can carry the maker's logo as logoUrl, for apps that draw a model picker. A company's logo is its trademark, so no logo ships with Nodaro. An install publishes only the logos it has the right to show. Every other maker's logoUrl is null, and apps then show the maker's name. An install that publishes no logo needs no setup.

To publish a maker's logo:

1. Upload the file to the bucket behind R2_PUBLIC_URL, at brand/makers/<maker id>.svg, with the content type image/svg+xml. Use the company's official logo as an SVG without scripts. The maker ids are the maker.id values that GET /v1/models returns.
2. Declare the maker ids in the instance setting model_maker_logos, a list such as ["google", "openai"]. On a Business install, the platform operator sets it with PUT /v1/admin/settings/model_maker_logos and the body {"value": ["google", "openai"]}. On the Community Edition, which has no admin panel, write the same instance setting directly in the database.

• The server checks the file first. A declared maker gets a logoUrl only once its file is in the bucket as an SVG, so the two steps can come in either order. A missing or wrongly typed file gives null, never a broken address.
• Never open the address in a browser to test an upload. The CDN, and Caddy on the bundled stack, keep a "not found" answer for a year. Check the file with the storage console or a HEAD request, such as curl -I.
• Timing. A new logo appears within about ten minutes. To replace a logo, upload the new file over the old one: the address changes with the file. To withdraw one, remove its id from the setting or delete the file.
• Nodaro never deletes these files. Remove a logo from the storage console when you mean to.

Default language

DEFAULT_LOCALE sets the language that a new visitor starts in. The values are he, ar, de, fr, es, hi, ja, ko, pt-BR, ru, zh-CN and en. A user's own saved choice always wins. An empty, blank or unknown value falls back to the visitor's browser language. Restart to apply. See Languages.

Tutorial packs

A self-hosted install can add its own tutorials to the built-in set, without a rebuild. Each pack is a directory:

• manifest.json — the pack's name and the categories its tutorials use, each with a slug, a name, and an optional sortOrder and description. Optional keys: locale, version, forbiddenPromptTerms, and creatorDisplayName, the author name shown on every card of the pack.
• One *.json file per tutorial — a workflow snapshot with its nodes, its connections and its results already made, so a clone opens showing the finished run. Optional card data: estimatedCredits, the credits a run costs, and estimatedPerMinuteCredits for a tutorial whose price follows the length of the recording it is given. Such a tutorial sets estimatedCredits to the fixed part and estimatedPerMinuteCredits to the credits per minute of the recording. Also optional: nodeTypesUsed and providersUsed for the chips on the card, a per-tutorial creatorDisplayName, and listedIn. listedIn is ["tutorial"] for the Tutorials tab, the default, or ["marketplace"] for the template marketplace. It applies only on the first seed.

Every media file a tutorial uses must be a public https:// URL. Each tutorial's category must be declared in the manifest, and it is created on the first boot.

Mount the pack directories into the container read-only, and list their paths inside the container:

  nodaro:
    volumes:
      - ./tutorials/acme:/data/tutorials/acme:ro

NODARO_TUTORIAL_PACKS=/data/tutorials/acme

Packs only add tutorials; they never change the built-in ones. A pack that fails validation is skipped whole and logged. Validation fails on invalid JSON, an undeclared category, a media URL that is not public, or a slug that collides with an existing tutorial. Restart the container to load a changed pack.

Social network apps

Publishing to a social network works per network. A network becomes available once its OAuth app credentials are set. Without them, the network still appears in Settings › Integrations as unavailable, with the names of the missing variables.

Every OAuth app must allow the redirect URI https://<your-domain>/v1/social/callback/<network>. When a Facebook or Instagram login manages more than one Page or account, the connect window asks the user which one to connect. See Publishing to social networks.