To make RESTBase useful to the public, we need to expose an end point. Requirements:
- HTTPS termination, ideally SPDY support (nginx 1.6?)
- a sensible subdomain
It is not clear whether caching would improve performance overall, so it's not part of the requirements. We can investigate that later. For now, we could set up nginx to listen on 80 & 443, using the existing *.wikimedia.org wildcard cert.
Candidates for the domain:
- api.wikimedia.org: simple and obvious domain, unused so far
- content.wikimedia.org: possibly less contentious; downsides: less obvious, would likely change in the longer term, longer, less accurate since not only content is exposed
- rest.wikimedia.org: simple and relatively general, if not *completely* obvious; provides a nice way to distinguish 'the action api' vs. 'the rest api' that we can keep for a while