Skip to content

feat: reverse proxy config#23

Merged
taygumus merged 4 commits intomainfrom
feat/reverse-proxy-config
Mar 3, 2026
Merged

feat: reverse proxy config#23
taygumus merged 4 commits intomainfrom
feat/reverse-proxy-config

Conversation

@taygumus
Copy link
Owner

@taygumus taygumus commented Mar 3, 2026

Reverse Proxy Configuration Refactor

Summary

This PR refactors the production setup to delegate HTTPS and certificate management to an external reverse proxy.

Changes

  • Removed Certbot service and related renewal/issue scripts
  • Removed certificate volumes and ACME challenge handling from the WordPress stack
  • Simplified production Nginx configuration to serve HTTP only
  • Attached the nginx service to the external proxy network
  • Introduced a stable Docker network alias (wp-docker-stack-nginx) for reverse proxy upstream resolution

Resulting Architecture

  • TLS termination handled by the reverse proxy
  • WordPress stack Nginx serves plain HTTP internally
  • Reverse proxy routes traffic via Docker network alias
  • Improved scalability and cleaner separation of concerns

This makes the stack production-ready, proxy-friendly, and easier to scale across multiple projects.

@taygumus taygumus self-assigned this Mar 3, 2026
@taygumus taygumus added the enhancement New feature or request label Mar 3, 2026
@taygumus taygumus merged commit 2227c39 into main Mar 3, 2026
4 checks passed
@taygumus taygumus deleted the feat/reverse-proxy-config branch March 3, 2026 21:26
@taygumus taygumus restored the feat/reverse-proxy-config branch March 21, 2026 18:14
@taygumus taygumus deleted the feat/reverse-proxy-config branch March 21, 2026 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant