sauladal

Dashboards listed alphabetically. I haven't set any of them up yet. Clearly there won't be a favorite among everyone. Some will be geared more toward fast set up, some for low resource usage, some for maximum customizability, some better for multiple users, others may be better for single user...

So which do YOU use? Why did you choose that one / what are your goals? What did you try before it and why did you move away from that one?

I'm going to set-up paperless-ngx but I'm struggling to fully understand the instructions for the docker-compose.yaml file (I'm new to docker-compose). Namely it's which volumes should be mapped and which don't need to be renamed. I'm setting this up on a Synology with 7.2 using Container Manager.

So following instructions from here and using docker-compose.postgres-tika.yml:

# docker-compose file for running paperless from the docker container registry.
# This file contains everything paperless needs to run.
# Paperless supports amd64, arm and arm64 hardware.
#
# All compose files of paperless configure paperless in the following way:
#
# - Paperless is (re)started on system boot, if it was running before shutdown.
# - Docker volumes for storing data are managed by Docker.
# - Folders for importing and exporting files are created in the same directory
#   as this file and mounted to the correct folders inside the container.
# - Paperless listens on port 8000.
#
# In addition to that, this docker-compose file adds the following optional
# configurations:
#
# - Instead of SQLite (default), PostgreSQL is used as the database server.
# - Apache Tika and Gotenberg servers are started with paperless and paperless
#   is configured to use these services. These provide support for consuming
#   Office documents (Word, Excel, Power Point and their LibreOffice counter-
#   parts.
#
# To install and update paperless with this file, do the following:
#
# - Copy this file as 'docker-compose.yml' and the files 'docker-compose.env'
#   and '.env' into a folder.
# - Run 'docker-compose pull'.
# - Run 'docker-compose run --rm webserver createsuperuser' to create a user.
# - Run 'docker-compose up -d'.
#
# For more extensive installation and update instructions, refer to the
# documentation.

version: "3.4"
services:
  broker:
    image: docker.io/library/redis:7
    restart: unless-stopped
    volumes:
      - redisdata:/data

  db:
    image: docker.io/library/postgres:15
    restart: unless-stopped
    volumes:
      - pgdata:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: paperless
      POSTGRES_USER: paperless
      POSTGRES_PASSWORD: paperless

  webserver:
    image: ghcr.io/paperless-ngx/paperless-ngx:latest
    user: 1029
    restart: unless-stopped
    depends_on:
      - db
      - broker
      - gotenberg
      - tika
    ports:
      - "8010:8000"
    healthcheck:
      test: ["CMD", "curl", "-fs", "-S", "--max-time", "2", "http://localhost:8000"]
      interval: 30s
      timeout: 10s
      retries: 5
    volumes:
      - data:/usr/src/paperless/data
      - media:/usr/src/paperless/media
      - ./export:/usr/src/paperless/export
      - ./consume:/usr/src/paperless/consume
    env_file: docker-compose.env
    environment:
      PAPERLESS_REDIS: redis://broker:6379
      PAPERLESS_DBHOST: db
      PAPERLESS_TIKA_ENABLED: 1
      PAPERLESS_TIKA_GOTENBERG_ENDPOINT: http://gotenberg:3000
      PAPERLESS_TIKA_ENDPOINT: http://tika:9998

  gotenberg:
    image: docker.io/gotenberg/gotenberg:7.8
    restart: unless-stopped

    # The gotenberg chromium route is used to convert .eml files. We do not
    # want to allow external content like tracking pixels or even javascript.
    command:
      - "gotenberg"
      - "--chromium-disable-javascript=true"
      - "--chromium-allow-list=file:///tmp/.*"

  tika:
    image: ghcr.io/paperless-ngx/tika:latest
    restart: unless-stopped

volumes:
  data:
  media:
  pgdata:
  redisdata:

Only changes I made so far above were a port change and adding a user id into webserver. For the volumes, the instructions only mention mapping the consume folder, but don't all of them need to be mapped in order to not get deleted with updates?

So "./consume:/usr/src/paperless/consume" needs to be "/volume1/docker/paperless/consume:/usr/src/paperless/consume" - right? But what about:

volumes:
  - redisdata:/data

volumes:
  - pgdata:/var/lib/postgresql/data

volumes:
  - data:/usr/src/paperless/data
  - media:/usr/src/paperless/media
  - ./export:/usr/src/paperless/export

Do all of those need to be changed? I assume yes and probably to just add "/volume1/docker/paperless/" to the start of each. Right?

But most importantly, I don't fully understand the top-level volumes element and how that comes into play or needs to be modified (from the bottom of the config):

volumes:
  data:
  media:
  pgdata:
  redisdata:

Hopefully someone can help or point me to where I can get this answered.

Thank you!