Files
configpolicy/group_vars/dch-proxy.yml
Dustin C. Hatch 168bfee911 r/webites: Add apps.du5t1n.xyz F-Droid repo
I want to publish the _20125_ Status application to an F-Droid
repository to make it easy for Tabitha to install and update.  F-Droid
repositories are similar to other package repositories: a collection of
packages and some metadata files.  Although there is a fully-fledged
server-side software package that can manage F-Droid repositories, it's
not required: the metadata files can be pre-generated and then hosted by
a static web server just fine.

This commit adds configuration for the web server and reverse proxy to
host the F-Droid repository at _apps.du5t1n.xyz_.
2024-11-05 06:47:02 -06:00

138 lines
2.8 KiB
YAML

dch_proxy_internal_networks:
- 172.30.0.0/16
- 172.31.1.0/24
# - 'fd68:c2d2:500e:3e00::/56'
dch_proxy_allowlist:
- 172.30.0.211/32
dch_proxy_blocklist:
- 172.30.0.208/28
- 172.30.0.224/29
- 172.30.0.232/29
- 172.30.0.240/28
dch_proxy_sites:
- backend: gitea
match: git.pyrocufflink
matcher: dom
- backend: bitwarden
match: bitwarden.pyrocufflink
matcher: dom
- backend: nextcloud
match: nextcloud.pyrocufflink.net
- backend: kubernetes
match: billing.hatchlearningcenter.org
- backend: web
match: chmod777.sh
matcher: end
- backend: web
match: dustinandtabitha.com
matcher: end
- backend: web
match: dustin.hatch.name
- backend: web
match: dustin.hatch.is
- backend: web
match: ebonfire.com
matcher: end
- backend: web
match: apps.du5t1n.xyz
- backend: web
match: hatchlearningcenter hlckc hlcks
matcher: dom
- backend: web
match: nratonpass.com
matcher: end
- backend: web
match: pyrocufflink.net
- backend: web
match: tabitha.biz
matcher: end
- backend: jellyfin
match: jellyfin.pyrocufflink
matcher: dom
- backend: kubernetes
match: ntfy.pyrocufflink.net
- backend: kubernetes
match: darkchestofwonders.us
- backend: kubernetes
match: invoiceninja.pyrocufflink.net
- backend: kubernetes
match: dynk8s-provisioner.pyrocufflink.net
dch_proxy_backends:
bitwarden:
servers:
- name: bitwarden
host: 'bitwarden.pyrocufflink.blue:80'
options: check
bitwarden-tls:
mode: tcp
servers:
- name: bitwarden
host: 'bitwarden.pyrocufflink.blue:443'
options: check
gitea:
servers:
- name: gitea
host: 'git0.pyrocufflink.blue:80'
options: check
gitea-tls:
mode: tcp
servers:
- name: gitea
host: 'git0.pyrocufflink.blue:443'
options: check
jellyfin:
servers:
- name: jellyfin
host: 'jellyfin.pyrocufflink.blue:80'
options: check
jellyfin-tls:
mode: tcp
servers:
- name: jellyfin-tls
host: 'jellyfin.pyrocufflink.blue:8443'
options: check send-proxy
kubernetes:
servers:
- name: k8s
host: 'k8s-ingress.pyrocufflink.blue:80'
options: check
kubernetes-tls:
mode: tcp
servers:
- name: k8s
host: 'k8s-ingress.pyrocufflink.blue:443'
options: check
nextcloud:
servers:
- name: nextcloud
host: 'cloud0.pyrocufflink.blue:80'
options: check
nextcloud-tls:
mode: tcp
servers:
- name: nextcloud
# NOTE: NOT the default HTTPS port, but a different virtual host that
# accepts the PROXY protocol
host: 'cloud0.pyrocufflink.blue:8443'
options: check send-proxy-v2
web:
servers:
- name: web0
host: 'web0.pyrocufflink.blue:80'
options: check
web-tls:
mode: tcp
servers:
- name: web0
host: 'web0.pyrocufflink.blue:443'
options: check