Bitflake logo
← Zurück zu Teammapper

Self-host Teammapper with Docker Compose

Schlankes, kollaboratives Mindmapping in Echtzeit für Teams, ganz ohne Anmeldung.

teammapper

postgres

postgres:18.3-alpine3.23

postgres-postgres-data-init

busybox

postgres-postgres-socket-init

busybox

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 Teammapper needs.
  3. Start Teammapper 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 Teammapper 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 Teammapper and save the file below into it as docker-compose.yml. It describes every container the stack needs — Teammapperitself 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:
  postgres:
    image: postgres:18.3-alpine3.23
    restart: unless-stopped
    network_mode: service:teammapper
    environment:
      PGDATA: /var/lib/postgresql/data
      POSTGRES_PASSWORD: ${RANDOM_PG_PASSWORD}
      POSTGRES_USER: app
    volumes:
      - postgres-data:/var/lib/postgresql/data
      - postgres-socket:/var/run/postgresql
    depends_on:
      postgres-postgres-data-init:
        condition: service_completed_successfully
      postgres-postgres-socket-init:
        condition: service_completed_successfully
  postgres-postgres-data-init:
    image: busybox
    volumes:
      - postgres-data:/var/lib/postgresql/data
    command:
      - chown
      - 70:70
      - /var/lib/postgresql/data
  postgres-postgres-socket-init:
    image: busybox
    volumes:
      - postgres-socket:/var/run/postgresql
    command:
      - chown
      - 70:70
      - /var/run/postgresql
  teammapper:
    image: ghcr.io/b310-digital/teammapper:latest
    restart: unless-stopped
    ports:
      - 3000:3000
    environment:
      BINDING: 0.0.0.0
      JWT_SECRET: ${RANDOM_JWT_SECRET}
      MODE: PRODUCTION
      POSTGRES_DATABASE: app
      POSTGRES_HOST: localhost
      POSTGRES_PASSWORD: ${RANDOM_PG_PASSWORD}
      POSTGRES_PORT: "5432"
      POSTGRES_QUERY_TIMEOUT: "10000"
      POSTGRES_SSL: "false"
      POSTGRES_STATEMENT_TIMEOUT: "10000"
      POSTGRES_USER: app
    healthcheck:
      test:
        - CMD
        - curl
        - -f
        - http://localhost:3000/
      interval: 10s
      timeout: 5s
      retries: 5
volumes:
  postgres-data: null
  postgres-socket: null

2. Secret generation

Teammapper 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 Teammapper with Docker Compose

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

Terminal

Start Teammapper 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:3000 in your browser.