Agent Skills › baserow/baserow › Add Django Config Env Var

Add Django Config Env Var

GitHub

用于在Baserow项目中新增Django配置环境变量，自动更新后端设置、Docker文件、前端映射及文档。适用于需同步修改多处配置文件以添加新环境变量的场景。

.agents/skills/add-django-config-env-var/SKILL.md baserow/baserow

Trigger Scenarios

需要新增Django环境变量参考INTEGRATION_LOCAL_BASEROW_PAGE_SIZE_LIMIT模式

Install

npx skills add baserow/baserow --skill Add Django Config Env Var -g -y

More Options

Non-standard path

npx skills add https://github.com/baserow/baserow/tree/develop/.agents/skills/add-django-config-env-var -g -y

Use without installing

npx skills use baserow/baserow@Add Django Config Env Var

指定 Agent (Claude Code)

npx skills add baserow/baserow --skill Add Django Config Env Var -a claude-code -g -y

安装 repo 全部 skill

npx skills add baserow/baserow --all -g -y

预览 repo 内 skill

npx skills add baserow/baserow --list

SKILL.md

Frontmatter

{
    "name": "Add Django Config Env Var",
    "version": "1.0.0",
    "description": "Add a new environment variable for a Django setting in Baserow and propagate it to the few repo files that usually need it. Use this when a request says a config env var must be added in several places or references `INTEGRATION_LOCAL_BASEROW_PAGE_SIZE_LIMIT` as the pattern to follow."
}

Add Django Config Env Var

Use INTEGRATION_LOCAL_BASEROW_PAGE_SIZE_LIMIT as the template. The env var name should be prefixed with BASEROW_ but the internal var isn't.

Keep the change simple and explicit. Do not add abstractions for this.

Files To Check

When adding a new setting, usually check these files:

backend/src/baserow/config/settings/base.py
docker-compose.yml
docker-compose.no-caddy.yml
web-frontend/env-remap.mjs
docs/installation/configuration.md — the canonical env-var reference table; add a row in the right section
Backend or frontend code that uses the setting
A focused test if behavior changes

Workflow

Add the Django setting in backend/src/baserow/config/settings/base.py near the closest related setting.

Example:

MY_SETTING = int(os.getenv("BASEROW_MY_SETTING", 123))

If the variable should be configurable in Docker, add it everywhere the similar example appears in:

docker-compose.yml
docker-compose.no-caddy.yml

If the frontend needs it at runtime, add it to web-frontend/env-remap.mjs.
Update consumers to use the setting:

Backend: settings.MY_SETTING
Tests: override_settings(MY_SETTING=...)

Add or update a targeted test if the setting changes behavior.
Add the related documentation in docs/installation/configuration.md — find the right section (e.g. Backend Configuration, Integration Configuration) and add a table row matching the format of the nearest existing entry.

Quick Checklist

Add it in base.py
Mirror the matching Docker entries
Add the Nuxt remap if frontend code needs it
Use settings.<NAME> in code
Add a focused test if needed
Add a row to docs/installation/configuration.md when necessary

Guardrails

Do not add a raw os.getenv(...) in application code when the value belongs in Django settings.
Do not update only one Docker location if the example appears in several places.
Do not expose a backend-only setting to Nuxt unless the frontend actually needs it.
Prefer copying the closest existing setting instead of inventing a new pattern.