Closed Darkspirit closed 5 years ago
r? @jdm
One thing to be aware of - I changed a webhook target for servo/servo from http://build.servo.org:9010 to https://build.servo.org:9010 and it broke everything.
One thing to be aware of - I changed a webhook target for servo/servo from http://build.servo.org:9010 to https://build.servo.org:9010 and it broke everything.
Oh dear. Of course, there is no starttls on an http port. I created another commit to introduce https://build.servo.org/github-buildbot/. Is this folder name okay or should we change it?
In the future, when all those plaintext services are behind nginx, they can be changed to only listen on 127.0.0.1. For github_buildbot.py it would be
reactor.listenTCP(options.port, site, interface='127.0.0.1')
(source 1, source 2).@jdm Should further changes be made, e.g. would you like to have a different name for the github_buildbot.py webhook, or is this ready to be merged? Thanks
:umbrella: The latest upstream changes (presumably #935) made this pull request unmergeable. Please resolve the merge conflicts.
https://github.com/servo/saltfs/pull/906#issuecomment-436313032
Problem: https://www.hardenize.com/report/build.servo.org#www_tls https://www.ssllabs.com/ssltest/analyze.html?d=build.servo.org&hideResults=on
server_tokens off;
makes nginx returnServer: nginx
without any version number.An nginx restart is needed:
service nginx restart
You can test withnginx -t
before restarting.This change is