Bitflake logo
← Back to Claper

Self-host Claper with Docker Compose

Turn your presentations into interactive conversations.

claper

postgres

postgres:18.3-alpine3.23

The steps below take a few minutes end to end.

  1. Docker compose setup and file
    save the generated compose and env files.
  2. Secret generation
    create the random passwords Claper needs.
  3. Start Claper with Docker Compose
    bring the stack up and check it's healthy.

Requirements

You'll need these installed on the machine you're deploying to:

Docker

Packages Claper and everything it depends on into an isolated container, so it runs the same way on your machine as it does everywhere else.

Install guide

Docker Compose

Reads docker-compose.ymland starts everything in it together. Ships with Docker Desktop. On Linux servers it's usually a separate install.

Install guide

1. Docker compose setup and file

Create a folder for Claper and save the file below into it as docker-compose.yml. It describes every container the stack needs — Claperitself and any supporting services, such as its database — along with the ports, volumes and environment variables each one uses. You'll also need an empty .env file in the same folder; Docker Compose reads it automatically and uses it to fill in the ${VARIABLE}references you'll see in the file below.

docker-compose.yml

version: "3.9"
services:
  claper:
    image: ghcr.io/claperco/claper:latest
    restart: unless-stopped
    ports:
      - 4000:4000
    environment:
      BASE_URL: http://localhost
      DATABASE_URL: postgresql://app:${RANDOM_PG_PASSWORD}@localhost:5432/app
      RANDOM_PG_PASSWORD: ${RANDOM_PG_PASSWORD}
      SECRET_KEY_BASE: ${RANDOM_SECRET_KEY_BASE}
    volumes:
      - uploads:/app/uploads
    healthcheck:
      test:
        - CMD
        - curl
        - -f
        - http://localhost:4000/
      interval: 10s
      timeout: 5s
      retries: 5
  postgres:
    image: postgres:18.3-alpine3.23
    restart: unless-stopped
    network_mode: service:claper
    environment:
      POSTGRES_PASSWORD: ${RANDOM_PG_PASSWORD}
      POSTGRES_USER: app
volumes:
  uploads: null

Volumes

Claper stores its data in named Docker volumes, so it survives container restarts and updates:

  • uploads mounted at /app/uploads

2. Secret generation

Claper needs a few randomly generated secrets — for example, database passwords or an internal session key — before it can start. These are referenced from docker-compose.ymlabove but don't live in it, so they need to end up in your .env file. Pick one of the two options below.

Generating secrets…

3. Start Claper with Docker Compose

From the folder with docker-compose.yml and .env, run:

Terminal

Start Claper and all its supporting services in the background.

docker compose up -d

The -d flag runs the stack in the background so it keeps running after you close the terminal. Docker will pull the images the first time, which can take a minute or two.

To check on it afterwards: docker compose ps shows whether containers are healthy, and docker compose logs -f follows their logs if something looks wrong. Once it's running, open http://localhost:4000 in your browser.