1
0
Fork 0
docker-easy-haproxy/tests_e2e/docker
Joao Gilberto Magalhaes 48f6e1f783 Migrate build assets and scripts to deploy/docker structure
- Removed `install.sh` and moved Docker-related assets to `deploy/docker`.
- Updated all Dockerfile references from `build/` to `deploy/docker/`.
- Refactored paths in E2E tests, Makefile, and documentation for consistency with new directory structure.
- Added `HAPROXY_STATS_CORS_ORIGIN` environment variable in `docker-compose.yml`.
2026-02-18 02:58:32 -05:00
..
php-app Migrate examples to tests_e2e directory structure 2026-02-12 17:05:04 -05:00
AGENTS.md Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-acme-e2e.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-acme.yml Add health checks for Docker services, ACME environment readiness validation, and Certbot unit tests 2026-02-16 11:47:28 -05:00
docker-compose-changed-label.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-cloudflare.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-ip-whitelist.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-jwt-validator.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-multi-containers.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-php-fpm.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-plugins-combined.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose-portainer-app-example.yml Migrate examples to tests_e2e directory structure 2026-02-12 17:05:04 -05:00
docker-compose-portainer.yml Add health checks for Docker services, ACME environment readiness validation, and Certbot unit tests 2026-02-16 11:47:28 -05:00
docker-compose-proxy-headers.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
docker-compose.yml Migrate build assets and scripts to deploy/docker structure 2026-02-18 02:58:32 -05:00
pebble-config.json Refactor ACME E2E tests: add Pebble health check container, simplify startup logic, and replace Python-based health check 2026-02-16 14:48:39 -05:00
README.md Migrate examples to tests_e2e directory structure 2026-02-12 17:05:04 -05:00

Docker Compose Examples

Self-contained examples for EasyHAProxy. All documentation is in the docker-compose files as header comments.

Quick Start

  1. Pick an example below
  2. Open the docker-compose file
  3. Read the header comments for complete instructions
  4. Run the commands step-by-step

Basic Examples

File Description
docker-compose.yml Basic SSL setup with two virtual hosts and stats interface
docker-compose-acme.yml Let's Encrypt SSL with automatic certificate generation
docker-compose-multi-containers.yml Load balancing across multiple container replicas
docker-compose-changed-label.yml Using custom label prefix (for multiple EasyHAProxy instances)

Real-World Application Examples

File Description
docker-compose-portainer.yml Portainer behind EasyHAProxy with Let's Encrypt
docker-compose-portainer-app-example.yml Additional app alongside Portainer (shared network)

Plugin Examples

File Description
docker-compose-php-fpm.yml FastCGI plugin with PHP-FPM and PATH_INFO routing
docker-compose-jwt-validator.yml JWT token validation for API protection
docker-compose-ip-whitelist.yml IP whitelist for admin panels or sensitive services
docker-compose-cloudflare.yml Restore real client IPs when behind Cloudflare CDN
docker-compose-plugins-combined.yml Multiple plugins combined for layered security

Documentation Structure

Each docker-compose file contains:

  • WHAT THIS DEMONSTRATES - Key features and concepts
  • REQUIREMENTS - Idempotent setup commands (safe to run multiple times)
  • HOW TO START - Command to launch the stack
  • HOW TO VERIFY IT'S WORKING - Test commands with expected outputs
  • CLEAN UP - Commands to stop and remove resources

Additional Documentation