Skip to content

feat(docker): add optional TLS/HTTPS support (#1896)#1934

Open
mrveiss wants to merge 1 commit intoDev_new_guifrom
fix/issue-1896
Open

feat(docker): add optional TLS/HTTPS support (#1896)#1934
mrveiss wants to merge 1 commit intoDev_new_guifrom
fix/issue-1896

Conversation

@mrveiss
Copy link
Owner

@mrveiss mrveiss commented Mar 19, 2026

Summary

  • Added docker/certs/generate-self-signed.sh for dev/testing certificates
  • Added docker/nginx/nginx-ssl.conf with HTTPS, HTTP→HTTPS redirect, security headers
  • Added cert volume mount to frontend service (reads from ./docker/certs/)
  • Added configurable nginx conf via AUTOBOT_NGINX_CONF env var
  • TLS is opt-in: default remains HTTP. Enable by setting env vars in .env.

Closes #1896

Test plan

  • Run bash docker/certs/generate-self-signed.sh — verify cert generation
  • Set AUTOBOT_NGINX_CONF=./docker/nginx/nginx-ssl.conf in .env
  • Run docker compose up -d — verify HTTPS on port 443
  • Verify HTTP→HTTPS redirect on port 80

- Add self-signed cert generation script at docker/certs/
- Add nginx-ssl.conf with HTTPS server block, HTTP->HTTPS redirect,
  TLS 1.2/1.3, and security headers (HSTS, X-Frame-Options, etc.)
- Add TLS volume mounts to frontend service in docker-compose.yml
- Add TLS env vars to .env.docker (commented out by default)
- TLS is opt-in: default remains HTTP-only
@github-actions
Copy link

✅ SSOT Configuration Compliance: Passing

🎉 No hardcoded values detected that have SSOT config equivalents!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant