# Settings for the Docker container. Copy this file to .env and edit it:
#
#   cp .env.example .env
#
# Every line is optional; leaving one out uses the default shown.

# --- Where you reach it -----------------------------------------------------

# Which address on this machine answers. The default keeps the analyzer to this
# machine, which is what you want for a tool with no login that reads a file
# full of your network's addresses, names and secrets.
#   127.0.0.1      this machine only
#   0.0.0.0        every interface, so anyone on the LAN can open it
#   192.168.1.10   one interface only
ANALYZER_BIND_IP=127.0.0.1

# The port on this machine. Inside the container it is always 8077.
ANALYZER_PORT=8077

# --- Storage ----------------------------------------------------------------

# Where extracted support files, cached analysis and cleaned exports are kept.
# The default is a Docker named volume, which Docker manages for you. Put a
# path here instead - ./data, or /srv/unifi-analyzer - to keep them in a
# directory you can open, back up or delete yourself.
ANALYZER_STORAGE=analyzer-data

# Support files put in this directory are imported when the container starts,
# so you do not have to upload a few hundred megabytes through the browser. It
# is mounted read-only: your originals are never modified.
ANALYZER_IMPORT_PATH=./import

# Empty storage every time the container starts or restarts. On by default: a
# support file holds real data about your network, and there is no reason for
# it to outlive the session that needed it. Set to false if you would rather
# keep bundles and their analysis - re-analysing a large file is not quick.
ANALYZER_CLEAR_ON_START=true

# Who owns the files written to storage. Only matters when ANALYZER_STORAGE is
# a directory on this machine; run `id -u` and `id -g` to see your own.
PUID=1000
PGID=1000