skills.rest
maxlainz
maxlainzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

futurefin-config-and-flags

Catalogs every FutureFin configuration axis with defaults, bounds, and parsing locations.

1|Updated May 2, 2026
Search Tags:#Docker#configuration#reference#rust#environment variables#docker-compose#self-hosted
One-click install
npx skills add https://github.com/maxlainz/FutureFin --skill futurefin-config-and-flags-maxlainz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: futurefin-config-and-flags
Source: https://github.com/maxlainz/FutureFin/tree/main/.claude/skills/futurefin-config-and-flags
Command: npx skills add https://github.com/maxlainz/FutureFin --skill futurefin-config-and-flags-maxlainz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? FutureFin configuration is split across three different parsers — the Rust API binary, the container entrypoint, and docker-compose — so options are frequently set in the wrong place, silently ignored, or rejected with a 400. This Skill is the single reference for what each option is called, its default, its validation bounds, and which file actually parses it. ## Core Features & Use Cases - Environment variable catalog: Documents every variable parsed by the API binary (PORT, DATABASE_URL, SESSION_TTL_DAYS, CORS_ORIGINS, FUTUREFIN_MCP_ENABLED, FUTUREFIN_PUBLIC_URL, and more) and by the container entrypoint (FUTUREFIN_DB_MODE, FUTUREFIN_BACKUP_KEEP*, POSTGRES_*), including silent-fallback quirks and startup panics. - Deployment and runtime settings: Covers the three docker-compose files, Home Assistant add-on option mapping, API query-parameter flags (?view=mine, ?months, ?density=hybrid), request-body limits, and PATCH /v1/installation settings such as base_currency, swr_pct, and mcp_write_enabled. - Use Case: When an env var "isn't taking effect", a setting change returns 400, CORS panics at startup, or you are adding a new env var, installation setting, or query param, load this Skill to find the exact parsing site, precedence rules, and version-specific behavior (3.0.0 self-contained image, 4.0.0 external DB retirement, 4.4.0 MCP hardening). ## Quick Start Ask the AI to look up the default, validation bounds, and parsing location of a specific FutureFin environment variable or installation setting.

Frequently Asked Questions about futurefin-config-and-flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is my FutureFin environment variable not taking effect?▼

FutureFin configuration is parsed by three different processes: the Rust binary, the container entrypoint, and docker-compose. A variable set in the wrong layer is silently ignored, and .env precedence rules can override compose values. Check which file parses the variable before setting it.

What happens if I set DATABASE_URL in the FutureFin container?▼

Since version 4.0.0, external databases were retired. A DATABASE_URL not pointing to the embedded Unix socket is ignored with a warning if a cluster exists, or causes the entrypoint to abort with a refuse_external_database error and exit code 1 if it does not.

Does FutureFin production require any environment variables?▼

No. Since the 3.0.0 self-contained image release, PostgreSQL 16 runs inside the single container over a Unix socket, so production runs with an empty .env file. All FUTUREFIN_* entrypoint variables have working defaults.

Why does FutureFin panic at startup with CORS_ORIGINS set?▼

CORS_ORIGINS entries must be parseable URLs; an unparseable entry or an empty resulting list panics at startup by design (fail-loud). The same fail-loud behavior applies to FUTUREFIN_PUBLIC_URL, FUTUREFIN_BASE_PATH, and FUTUREFIN_TRUSTED_PROXY_IPS.

How do I disable the MCP server in FutureFin?▼

Set FUTUREFIN_MCP_ENABLED=0. Since 4.4.0 the /mcp and OAuth protocol routes stay mounted but return 404 JSON with code mcp_disabled instead of being unmounted, and credential-revocation endpoints like /v1/api-tokens remain available.

When should I not use the FutureFin configuration catalog?▼

Do not use it for step-by-step environment setup, deployment, upgrades, backups, or understanding the FIRE math behind the settings. Those belong to the build-and-env, run-and-operate, and fire-domain-reference skills respectively.

Related Skills

Explore More Software Engineering Skills→
nixopusnixopus

dev-setup

Automate local development setup with Node.js, Yarn, PostgreSQL, and Redis.

Official
Intermediate
Xipher-LabsXipher-Labs
6

vercel-cli

Automates deployments and rollback via the official Vercel CLI.

Official
Intermediate
aiunlocked1412aiunlocked1412
14

financial-planner

Generate personalized financial plans for Thai users with configurable assumptions.

Community
Advanced
GetFresh-VenturesGetFresh-Ventures

verify-execution

Verify code changes by observing runtime outputs on CLI, API, or GUI surfaces.

Official
Intermediate