Self-host WiseMapping with Docker Compose

Browserbasiertes Mindmapping mit Echtzeit-Zusammenarbeit zum Planen und Teilen von Ideen.

wisemapping

postgres

postgres:18.3-alpine3.23

postgres-postgres-data-init

busybox

postgres-postgres-socket-init

busybox

This is still a work in progress.

The generated compose file and instructions may not be complete or correct for every app yet. Please report any issues you encounter to contact@bitflake.com.

The steps below take a few minutes end to end.

Docker compose setup and file
save the generated compose and env files.
Secret generation
create the random passwords WiseMapping needs.
Start WiseMapping 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 WiseMapping 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 WiseMapping and save the file below into it as docker-compose.yml. It describes every container the stack needs — WiseMappingitself 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
    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
  wisemapping:
    image: wisemapping/wisemapping:latest
    restart: unless-stopped
    ports:
      - 80:80
    environment:
      APP_JWT_SECRET: ${RANDOM_APP_JWT_SECRET}
      APP_OAUTH_TOKEN_SECRET: ${RANDOM_APP_OAUTH_TOKEN_SECRET}
      APP_REGISTRATION_EMAIL_CONFIRMATION_ENABLED: "false"
      APP_SITE_API_BASE_URL: http://wisemapping.localhost:80
      APP_SITE_UI_BASE_URL: http://wisemapping.localhost:80
      JAVA_OPTS: -XX:InitialRAMPercentage=50 -XX:MaxRAMPercentage=70
      SPRING_DATASOURCE_DRIVER_CLASS_NAME: org.postgresql.Driver
      SPRING_DATASOURCE_PASSWORD: ${RANDOM_PG_PASSWORD}
      SPRING_DATASOURCE_URL: jdbc:postgresql://localhost:5432/app
      SPRING_DATASOURCE_USERNAME: app
      SPRING_JPA_HIBERNATE_DDL_AUTO: validate
      SPRING_JPA_PROPERTIES_HIBERNATE_DIALECT: org.hibernate.dialect.PostgreSQLDialect
      SPRING_SQL_INIT_CONTINUE_ON_ERROR: "false"
      SPRING_SQL_INIT_DATA_LOCATIONS: classpath:data-postgresql.sql
      SPRING_SQL_INIT_MODE: always
      SPRING_SQL_INIT_PLATFORM: postgresql
      SPRING_SQL_INIT_SCHEMA_LOCATIONS: classpath:schema-postgresql.sql
    depends_on:
      postgres:
        condition: service_started
volumes:
  postgres-data: null
  postgres-socket: null

2. Secret generation

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

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

Terminal

Start WiseMapping 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:80 in your browser.