docker-compose.yml

#
# ==== THIS FILE IS NOT ACTIVELY USED OR MAINTAINED! ====
#
# This config is an example when using STM without a reverse proxy. All hosted versions of STM use a reverse proxy,
# which handles path rewrites and SSL certificates. See the hosting documentation for further information on the usage
# of a reverse proxy.
#

services:
  stm-server:
    image: simpletaskmanager/stm-server:1.7.1
    container_name: stm-server
    environment:
      - STM_OAUTH2_CLIENT_ID
      - STM_OAUTH2_SECRET
      - STM_DB_USERNAME
      - STM_DB_PASSWORD
      - STM_DB_HOST
    network_mode: host
    volumes:
      - /etc/letsencrypt:/etc/letsencrypt
      - $STM_SERVER_CONFIG:/stm-server/config.json
# 2020-12-09 hauke96: See systemd issue below
#    depends_on:
#      - "stm-db"
    logging:
      driver: 'journald'
  stm-client:
    image: simpletaskmanager/stm-client:1.7.1
    container_name: stm-client
    network_mode: host
    volumes:
      - /etc/letsencrypt:/etc/letsencrypt
      - $STM_NGINX_CONFIG:/etc/nginx/conf.d/default.conf
      # This allows you to show arbitrary notes on the login screen (e.g. to inform user about maintenance):
      #- ./notice.de.html:/usr/share/nginx/html/assets/i18n/notice.de.html
    logging:
      driver: 'journald'
  stm-db:
    image: postgres:17
    container_name: stm-db
    network_mode: host
    environment:
      - POSTGRES_USER=${STM_DB_USERNAME}
      - POSTGRES_PASSWORD=${STM_DB_PASSWORD}
    volumes:
      - ./postgres-data:/var/lib/postgresql/data
# 2020-12-09 hauke96: Because health checks are creating mount points, newer
# systemd versions are flodding the logs with succeed-messages rendering the
# logs more or less useless, because they are way too large. I disable health
# checks here until there's a solution for that.
#
#    healthcheck:
#      test: ["CMD-SHELL", "pg_isready -U ${STM_DB_USERNAME}"]
#      interval: 1s
#      timeout: 2s
#      retries: 30
#      start_period: 1s
    logging:
      driver: 'journald'