.env.example

# Timezone for the container (e.g. America/New_York, Europe/London, Asia/Tokyo)
TZ=America/New_York

# Host user/group IDs — must match the user running Docker to avoid permission issues
# Run `id -u` for PUID and `id -g` for PGID
PUID=1000
PGID=1000

# Route ALL Chromium traffic through WireGuard VPN
# true  — start with WireGuard; requires a .conf file placed in the vpn/ directory
# false — normal operation, no VPN (default)
# Always start with ./scripts/start.sh — it reads this value and selects the correct compose stack
USE_VPN=false

# Ports to expose on the host
# HTTP  — no cert warning, works on all clients
HTTP_PORT=3000
# HTTPS — self-signed cert; client will show a security warning on first visit (safe to proceed)
HTTPS_PORT=3001

# Start with a clean browser on every container start
# true  — wipes Chromium profile (bookmarks, history, cookies) each time the container starts
# false — retains all browser data across restarts (default)
CLEAN_START=false

# Browser login credentials
# CHROME_PASSWORD is required — there is no default and the container won't be protected without it
CHROME_USER=admin
CHROME_PASSWORD=your-strong-password-here

# Shared memory allocated to the container
# Chrome crashes or shows a blank tab if this is too low — keep at 1gb minimum, 2gb recommended
SHM_SIZE=2gb

# Resource limits applied to the container
# Set to ~70% of host resources to leave headroom for the OS and other processes
# Formula: CPU_LIMIT = total_cores * 0.7 | MEM_LIMIT = total_ram_gb * 0.7
CPU_LIMIT=8.4
MEM_LIMIT=11G