9f25c1cb09
The idea of proxying in front of Garage may be warranted, to handle some of the ways that it subdomains further. However, I'm not there yet.
38 lines
1007 B
Plaintext
38 lines
1007 B
Plaintext
{
|
|
debug
|
|
}
|
|
|
|
# I feel like a proxy in front of Garage (within the container)
|
|
# would let me redirect `/health` from the TLD through to the admin API,
|
|
# which is the only place the healthcheck URL exists. But, Cloudron has no notion
|
|
# of the healthcheck being somewhere else.
|
|
|
|
# https://garagehq.deuxfleurs.fr/documentation/cookbook/reverse-proxy/
|
|
s3.garage.tld, *.s3.garage.tld {
|
|
reverse_proxy localhost:3900 {
|
|
health_uri /health
|
|
health_port 3903
|
|
#health_interval 15s
|
|
#health_timeout 5s
|
|
}
|
|
}
|
|
|
|
# These would need to be templated, I think, so they match the domain
|
|
# that is coming in to the container.
|
|
*.web.garage.tld {
|
|
reverse_proxy localhost:3902 {
|
|
health_uri /health
|
|
health_port 3903
|
|
#health_interval 15s
|
|
#health_timeout 5s
|
|
}
|
|
}
|
|
|
|
admin.garage.tld {
|
|
reverse_proxy localhost:3903 {
|
|
health_uri /health
|
|
health_port 3903
|
|
#health_interval 15s
|
|
#health_timeout 5s
|
|
}
|
|
} |