Configuration

Rotion is configured with environment variables, or in code with configure. The variables are read each time Rotion uses them, so they only have to be set before the first fetch: in .env.local for Next.js, in the CI job’s environment, or on the command line.

NOTION_TOKEN=ntn_xxx ROTION_INCREMENTAL_CACHE=true npm run build

Variables

Boolean variables are enabled only by the exact string true. Numeric values are parsed as integers.

Paths in ROTION_CACHEDIR and ROTION_DOCROOT are relative to the current working directory, and so is the package.json that gives the default ROTION_UA.

Configure in code

configure sets the same settings from code. A value given to it wins over its environment variable. Use it when environment variables are inconvenient: a framework that does not put .env into process.env, such as Astro’s import.meta.env, or a token that comes from somewhere else.

import { configure } from 'rotion'
 
configure({
  auth: import.meta.env.NOTION_TOKEN,
  docRoot: 'storage',
  incrementalCache: true,
})

Call it before the first fetch. A later call adds to the earlier ones, and undefined goes back to the environment variable. The settings are process-wide.

Variables used by the examples

NOTION_DATABASE_ID, used throughout these docs and in the examples, is not read by Rotion. The examples read it in their own code and pass it to FetchDatabase.