directlx 9be34947b2 Fix www.directlx.dev accessibility with nginx firewall and DNS config ... This commit resolves connectivity issues for www.directlx.dev by: 1. Add nginx firewall configuration (host_vars/nginx.yml) - Allow ports 80/tcp (HTTP) and 443/tcp (HTTPS) - Enables NPM to proxy traffic to nginx backend 2. Add www.directlx.dev DNS record via Pi-hole - Configure playbooks/configure-directlx-dev-dns.yml - Route www.directlx.dev → NPM (192.168.200.71) - NPM then proxies to nginx (192.168.200.65) Problem: After firewall changes, nginx server only allowed SSH (port 22), blocking HTTP/HTTPS from NPM. Additionally, Pi-hole had no DNS record for www.directlx.dev subdomain. Solution: Applied firewall rules and DNS configuration to complete the proxy chain: Browser → Pi-hole DNS → NPM → nginx. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-02-14 09:14:59 -05:00
..
docker.yml	Add host_vars for firewall configuration	2026-02-04 09:49:31 -05:00
hiveops.yml	Enable MySQL connectivity for Docker applications	2026-02-06 11:30:14 -05:00
jenkins.yml	Add comprehensive security audit and Jenkins connectivity fixes	2026-02-09 13:27:36 -05:00
mysql.yml	Enable MySQL connectivity for Docker applications	2026-02-06 11:30:14 -05:00
nginx.yml	Fix www.directlx.dev accessibility with nginx firewall and DNS config	2026-02-14 09:14:59 -05:00
npm.yml	Add comprehensive security audit and Jenkins connectivity fixes	2026-02-09 13:27:36 -05:00
pihole.yml	Add Pi-hole host_vars for firewall ports	2026-02-04 09:25:46 -05:00
smartjournal.yml	Enable MySQL connectivity for Docker applications	2026-02-06 11:30:14 -05:00