DescriptionUpdate web infrastructure
* Use https for outgoing links throughout
This avoids mixed mode content on https://lilypond.org
* Use https for lilypond.org; As of today, Thu 13 Feb, lilypond.org
serves on HTTPS.
* Remove mentions of Virginia Tech and webdev.nl
For posterity, this is how lilypond.org was serving before today:
* Jan & Han-Wen are admins of a Google Cloud Platform project
* In the GCP project, we have
- a backend apache-instance-group serving from us-central1-a
- a single VM running apache on in 'apache-instance-group'
- a static IP pointing to the 'apache-instance-group'
Today, I added
- a load balancer 'lilypond', serving on port 80 and 443 of static
IP 35.206.114.173
- a google-managed certificate for 'lilypond.org', on the load balancer
Then, I changed lilypond.org DNS to point to 35.206.114.173
Patch Set 1 #Patch Set 2 : perl #
MessagesTotal messages: 3
|