Deploy production HTTPS bouncer, collector and web_connectivity test helper

[hellais]

This ticket is about updating the canonical bouncer, collector and web_connectivity test helper to support.

I believe the bouncer YAML configuration file should look something like this:

collector:
  httpo://ihiderha53f36lsd.onion:
    collector-alternate:
    - {address: 'https://a.collector.ooni.io', type: 'https'}
    test-helper: {dns: '213.138.109.232:57004', ssl: 'https://213.138.109.232', tcp-echo: '213.138.109.232', traceroute: '213.138.109.232', web-connectivity: 'httpo://7jne2rpg5lsaqs6b.onion'}
    test-helper-alternate:
        web-connectivity:
        - {address: 'https://web-connectivity.ooni.io', type: 'https'}

Let me know if you need some A records to be setup for this.

[hellais]

This is blocking on us being able to make the 1.6.0 release of ooniprobe.

[anadahz]

@hellais I guess you mean testing instead of production?
A testing ooni-backend with HTTPS bouncer, collector and web_connectivity test helper is up and running.

[hellais]

No, this is related to the deployment of the production HTTPS collector, bouncer and web_connectivity helper #58 is for the testing ones.

[anadahz]

Isn't better to test new features in a testing deployment?

[hellais]

Of course, but we need to have the production one deployed before ooniprobe 1.6.0 is released.

[anadahz]

OK we then need another ticket for that since this will be another deployment.

[hellais]

Sorry for not making it clearer that this is about the "production deployment" that should be deployed once we have tested it as described in #58.

[anadahz]

This has been done, tested and deployed.