Streamline testing environment: minimal compose setup with UI volume mount

[Copilot]

Repo contained 16 docker-compose variants and configs for MySQL, proxies, and auxiliary services. Testing required wading through unnecessary complexity.

Changes

Minimal testing setup (docker-compose_test.yaml)

• 5 core services: PostgreSQL, Zabbix Server, Web UI (Nginx), DB init, data container
• Optional agent via --profile agent
• 67% fewer services than full setup (5 vs 15 with --profile all)

UI volume mount for customization

volumes:
  - ${DATA_DIRECTORY}/usr/share/zabbix/ui:/usr/share/zabbix/ui:rw

Applied to both docker-compose_test.yaml and docker-compose_v3_ubuntu_pgsql_latest.yaml

Removed unnecessary files (51 total, 6,577 lines)

• 14 docker-compose variants (Alpine, CentOS, Oracle Linux, MySQL)
• 14 env_vars files (MySQL creds, proxy, java-gateway, snmptraps, web-service)
• 23 config_templates (proxy, web-service)

Updated symlink

• compose.yaml → docker-compose_test.yaml (was pointing to deleted Alpine variant)

Usage

# Minimal (new default)
docker compose up

# With agent
docker compose --profile agent up

# Full setup (preserved)
docker compose -f docker-compose_v3_ubuntu_pgsql_latest.yaml up

UI customization: ./zbx_env/usr/share/zabbix/ui/

Documentation

Added: TESTING.md, QUICKSTART.md, CLEANUP_SUMMARY.md, IMPLEMENTATION.md, verify-setup.sh

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.