app-sidecar

Configure and manage sidecar containers alongside FuseBase app backends and cron jobs.

5|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ryan-haver/fusebase-mcp --skill app-sidecar-ryan-haver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-sidecar
Source: https://github.com/ryan-haver/fusebase-mcp/tree/main/apps/client-portal-dashboard/.claude/skills/app-sidecar
Command: npx skills add https://github.com/ryan-haver/fusebase-mcp --skill app-sidecar-ryan-haver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? App backends often need auxiliary services like headless browsers, caches, or image processors, but wiring up companion containers with correct networking, secrets, and resource limits is error-prone. This Skill guides the full lifecycle of sidecar containers in FuseBase apps. ## Core Features & Use Cases - Sidecar Lifecycle Management: Add, remove, and list sidecar containers via the fusebase sidecar CLI commands for both backends and cron jobs. - Secrets & Environment Control: Whitelist registered app secrets per sidecar with KEY or KEY:ALIAS forms, and configure isolated environment variables. - Resource & Networking Rules: Enforce tier sizing (small/medium/large), the 2 CPU / 4 Gi total budget, localhost networking, and the reserved port 3000 constraint. - Use Case: A scraping app needs a headless browser. Add a browserless/chrome sidecar on port 9222 with a medium tier, then have the backend call it at http://localhost:9222 after fusebase deploy. ## Quick Start Add a chromium sidecar to my-scraper using the browserless/chrome image on port 9222 with a medium resource tier.

Frequently Asked Questions about app-sidecar

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

FAQPage Schema
How do I add a sidecar container to a FuseBase app?▼

Run fusebase sidecar add with --app, --name, and --image flags, plus optional --port, --tier, --env, and --secret options. The app must have a backend folder configured in fusebase.json, and sidecars deploy automatically with fusebase deploy.

How do sidecar containers communicate with the backend?▼

Sidecars share the backend's network namespace, so the backend reaches them over localhost on their configured port, such as http://localhost:9222 for a headless browser. Port 3000 is reserved for the backend and must not be used by sidecars.

Can cron jobs have their own sidecar containers?▼

Yes, use fusebase sidecar add with the --job flag to attach sidecars to a specific cron job. Job sidecars run in the job replica's network namespace, are isolated from backend sidecars, and have their own independent 3-sidecar limit.

Do sidecars receive app secrets automatically?▼

No, sidecars receive no app secrets by default. Whitelist specific keys with the repeatable --secret flag on sidecar add, using KEY to keep the name or KEY:ALIAS to rename the env var inside the sidecar.

What are the limitations of sidecar containers?▼

Each app supports at most 3 sidecars, only pre-built Docker images are allowed, and sidecars do not run during local fusebase dev start. Total CPU and memory across the backend and all sidecars must stay within 2 CPU and 4 Gi.

Why is my sidecar not available after deployment?▼

Check container logs with fusebase remote-logs runtime <appId> --container <name> and inspect system logs with --type system. Common causes include the sidecar binding to reserved port 3000 or exceeding the Azure resource budget.