Environment Variables

TapMap supports a small set of environment variables that override the default runtime configuration.

TapMap works without environment variables and uses sensible defaults.

Environment variables allow specific settings to be overridden without modifying the source code or rebuilding the application.

Common uses include:

Using a different port when the default port is already in use.
Storing application data in a custom location.
Using a fixed location instead of automatic public-IP based location detection.
Configuring TapMap when running in Docker.

TAPMAP_PORT

Override the HTTP port used by the local Dash server.

Default:

Examples:

Linux / macOS:

TAPMAP_PORT=8060 tapmap

PowerShell:

$env:TAPMAP_PORT="8060"
tapmap.exe

Command Prompt:

set TAPMAP_PORT=8060
tapmap.exe

This setting is useful when the default port is already in use.

TAPMAP_HOST

Override the server bind address.

Example:

TAPMAP_HOST=0.0.0.0 tapmap

If not specified, TapMap normally binds to:

127.0.0.1

When running in Docker, TapMap uses:

0.0.0.0

unless overridden by TAPMAP_HOST.

The default Docker setting allows TapMap to be accessed from other machines on the network.

TAPMAP_IN_DOCKER

Tell TapMap that it is running in Docker.

Docker deployments use:

TAPMAP_IN_DOCKER=1

This changes Docker-specific runtime behavior, including the default server bind address and disabling desktop-only features such as the system tray and autostart.

The Docker Compose configuration sets this variable automatically. When using docker run, set it explicitly as shown in the Docker examples.

TAPMAP_DATA_DIR

Override the application data directory.

By default, TapMap uses the operating system's standard per-user application data location.

The data directory contains:

GeoIP databases
README.txt
Application-generated data

This setting is useful when you want to store TapMap data in a custom location.

TAPMAP_LON and TAPMAP_LAT

Override automatic public-IP based location detection.

Both variables must be provided together.

Example:

TAPMAP_LON=10.7522 TAPMAP_LAT=59.9139 tapmap

If both values are present and valid, TapMap uses the specified coordinates for the local map marker.

If either value is missing or invalid, TapMap falls back to the configured location behavior.

This setting is useful when automatic location detection is inaccurate or when you prefer not to use public-IP based location detection.

TAPMAP_LAUNCH_BROWSER

Control whether TapMap automatically opens the default web browser at startup.

Default:

true

Values:

true
false

Example:

TAPMAP_LAUNCH_BROWSER=false tapmap

The --no-browser command-line flag overrides this setting.

TapMap's Run TapMap automatically feature already starts TapMap without opening the browser, so this setting is not required for desktop autostart.

TAPMAP_CACHE_RETENTION_MIN

Control how long inactive services remain visible on the map.

Default:

Values:

0     Keep cached services until Clear cache is used.
>0    Remove cached services not seen for the specified number of minutes.

Example:

TAPMAP_CACHE_RETENTION_MIN=15 tapmap

This setting affects only the map cache.

It does not affect the current network snapshot, Open Ports, LAN/LOCAL Services, Unmapped Services, or the 30-day Insights history.

TAPMAP_NOTIFICATION_LEARNING_DAYS

Control how many active Insights days TapMap waits before sending notifications.

Default:

Values:

0–30

A value of 0 enables notifications immediately.

Example:

TAPMAP_NOTIFICATION_LEARNING_DAYS=0 tapmap

The learning period affects notifications only. Significant Connections are recorded during the learning period.