The confiruation we use for testing, and then roll into production, is at
https://github.com/crkn-rcdr/Access-Platform/tree/main/services/haproxy
This repo contains an example HAProxy config for setting up a Canadiana platform development environment, along with the error pages we use when services are down.
$ cp haproxy.cfg.example haproxy.cfg
$ echo whatevertextyoulike > pass.txt
$ ./generate_test_cert.sh
$ docker-compose up
The test cert script creates a Certificate Authority, and then signs the local server's certificate with said authority. You can import the certificate authority information into your browser. In Chrome, look for Manage Certificates in settings, and import ./certs/ca.pem under the Authorities tab.
The HAProxy config should work out of the box, although feel free to meddle with it (which is why haproxy.cfg is in .gitignore). Default Docker network configs for Access platform repos will assume that HAProxy is running on your machine.
The default config supports the following projects:
If these services are running on your machine, and you've edited your /etc/hosts file to point their public domains locally, you should be able to access these services as if they were running in production (i.e. no need to specify ports, etc.). Please check each project for local setup instructions. This config supports adding a suffix to each subdomain, e.g. auth-dev.canadiana.ca, if you want to maintain access to both local installations and production installations running at e.g. auth.canadiana.ca.