# nextasks, start with:  docker compose up -d --build
#
# Then open http://<your-host>:8510. The first account you create there is the operator; it needs the setup code
# from the log (docker logs nextasks) or the one you set below.

services:
  nextasks:
    build: .
    container_name: nextasks
    restart: unless-stopped

    ports:
      # Host port on the left, container port on the right.
      - "8510:8000"

    volumes:
      # Database, files of the tasks (data/media), logs, backups and the operator's own languages.
      # A local disk, never an SMB or NFS share: SQLite's locking does not work reliably over network filesystems.
      - ./data:/data

    environment:
      # Who should own the files in the data directory. The container fixes the permissions itself on startup.
      PUID: 1000
      PGID: 1000

      TZ: Europe/Berlin

      # The address people use to reach nextasks, for invitation links, the QR code of the app and the redirect
      # address of the sign-in providers. Can also be set in the interface.
      # NEXTASKS_PUBLIC_URL: https://tasks.example.com

      # Behind a reverse proxy: its address, so that the brake against password guessing sees the real sender. The
      # list also makes its X-Forwarded-Proto believable (https), for the sign-in address and the cookie.
      # NEXTASKS_TRUSTED_PROXIES: 172.16.0.0/12

      # The code the first account needs. Without it nextasks makes one at every start until it is set up and
      # writes it to the log: docker logs nextasks
      # NEXTASKS_SETUP_TOKEN: choose-a-long-one

      # The largest attachment in megabytes, at most 50 (the operator can lower it in the settings).
      # NEXTASKS_UPLOAD_MAX_MB: 50

      # The relay that hands notifications to Apple for the iPhone app; only encrypted messages go there.
      # Empty: nothing goes out, the app plans its own reminders.
      # NEXTASKS_PUSH_RELAY: https://push.nexapps.dev