Configurable host port mappings via environment variables

[nelsonni]

Problem: The docker-compose.yml hardcodes 80:80 and 443:443 for the nginx service (here). Users running TimeTracker behind a reverse proxy (e.g., Pangolin, Nginx Proxy Manager, Traefik) on a server where port 80/443 are already in use cannot deploy without manually editing docker-compose.yml, which creates git divergence and breaks future upstream updates.

Solution: Replace the hardcoded port mappings with environment variables with sensible defaults:

ports:
  - "${HTTP_PORT:-80}:80"
  - "${HTTPS_PORT:-443}:443"

Users behind a reverse proxy could then set HTTP_PORT=8180 and HTTPS_PORT=8443 in their .env file.

Value: This is a common self-hosting pattern and would make TimeTracker significantly easier to deploy in homelab and multi-service environments without requiring local modifications to tracked files.

[evilguy4000]

@nelsonni can you test with v4.21.2

[nelsonni]

@DRYTRIX I can confirm that v4.21.2 and port mappings via HTTP_PORT and HTTPS_PORT resolved the original issue. During the upgrade process I did run into a related OIDC issue that I've documented in #566 in case it's useful.