featbit-deployment-docker

Deploy FeatBit with Docker Compose across three configuration tiers.

11|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/featbit/featbit-skills --skill featbit-deployment-docker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: featbit-deployment-docker
Source: https://github.com/featbit/featbit-skills/tree/main/skills/featbit-deployment-docker
Command: npx skills add https://github.com/featbit/featbit-skills --skill featbit-deployment-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FeatBit deployments often require varied Docker Compose configurations across multiple tiers. This skill provides a guided blueprint to simplify setting up and reproducing FeatBit environments with Docker.

Core Features & Use Cases

  • Tiered deployment guides for Standalone (PostgreSQL only), Standard (PostgreSQL/MongoDB + Redis), and Professional (+ Kafka + ClickHouse).
  • Environment variable mapping, docker-compose file references, and production-readiness considerations for local development, staging, and production.
  • Clear recommendations on when to choose each tier and how to migrate between tiers as demand grows.

Quick Start

Clone the FeatBit repository, choose a deployment tier, and start services with the appropriate docker-compose command.

Frequently Asked Questions about featbit-deployment-docker

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

FAQPage Schema
How do I deploy FeatBit locally using Docker Compose?▼

Deploy FeatBit using Docker Compose by cloning the repository, selecting a deployment tier, and running the appropriate docker-compose command to start the configured services for your environment.

What are the differences between FeatBit Standalone, Standard, and Professional deployment tiers?▼

FeatBit deployment tiers scale from Standalone using PostgreSQL only, to Standard adding MongoDB and Redis, up to Professional incorporating Kafka and ClickHouse for advanced production readiness.

When should I upgrade my FeatBit Docker deployment from Standalone to Standard?▼

Upgrade your FeatBit Docker deployment from Standalone to Standard when your infrastructure requires Redis caching and MongoDB data storage to handle increased scalability and production-level demand.

Do I need Kafka and ClickHouse to run FeatBit with Docker Compose?▼

Kafka and ClickHouse are only required for the Professional deployment tier. Standalone and Standard FeatBit Docker deployments operate without them, relying on PostgreSQL, MongoDB, and Redis configurations.

How do I configure environment variables for a FeatBit Docker Compose deployment?▼

Configure FeatBit Docker deployments by mapping environment variables within the docker-compose files to ensure correct service definitions, health checks, and data persistence across the chosen tier.

What production-readiness considerations exist for FeatBit Docker deployments?▼

FeatBit Docker production-readiness involves configuring tier-specific prerequisites, ensuring data persistence, defining health checks, and mapping environment variables correctly across Standalone, Standard, and Professional tiers.