Document HTTPS support

[markmetcalfe]

Having HTTPS support with our sites may be useful to have. It would give the advantage of letting us save common login password info, marginally increase page load speed, and would stop that warning message when installing/upgrading totara via the web UI.

To implement this we would need to add a server {} directive for the 443 port in the nginx server.conf, and would need to create a root certificate that supports all the totaraXX/totaraXX.debug hosts. Then the dev using docker-dev would need to manually add the root cert to their system's trusted certs.

[derschatta]

HTTPS support is already there :)

[derschatta]

It's just not documented

[derschatta]

hm doesn't seem to work anymore, need to check and fix it

[markmetcalfe]

Yeah ideally this repo would include a pem/key so you can easily add it to your host system's trusted certs - I don't see the cert file currently.

[derschatta]

started to improve this but it turns out to be a bit more complicated than I expected to set up a CA and have a certificate verified by it. Currently, the built-in https support works in all browser but Chrome. Just access the site via https://totara73 for example. You get a warning as the certificate is self-signed but in all browser except Chrome you can accept and continue.

[elkbullwinkle]

You can add your root cert into the keychain on the mac and make it trusted, it will make all the certs signed by that one trusted on your computer.

[markmetcalfe]

So the solution to this then is just adding instructions to the README on how to add the totara cert as a trusted CA on each platform