Publish documentation on clusterhq.com

[robhaswell]

No description provided.

[itamarst]

1. We should probably wait until we have open source release and project name.
2. We should use our own domain.
3. We will want to use our own theme... we need to make sure RTD supports this.

Also, automating releases on RTD may not be possible, so we might just decide it's better to host our own.

[wallrj]

Project name is decided and it's now open source. So moved this from blocked to ready.

[lukemarsden]

Let's put this at clusterhq.com/docs, as a static content sphinx build. You can upload to that via SCP. Buildbot already does sort of automatic upload for docs.hybridcluster.com.

[lukemarsden]

(Let me know if you'd like me to configure a SSH public key to be able to authenticate to clusterhq.com).

[tomprince]

The release process (#293) currently builds docs on RTD, which show up at docs.clusterhq.com. It would also be possible to proxy to RTD (from cloudfront?), to get it show up at at /docs.

If buildbot is going to upload docs automatically, the SSH key shouldn't ever touch the slaves, it should just be on the master. (Eventually the slaves are probably going to be running somewhat untrusted code).

On the other hand, while I think the release process should be automated, I don't think the thing that triggers that automation should be somebody creating a tag or a branch in the repository.

[robhaswell]

Our website will be converted to Docker hosting with an nginx frontend (https://www.pivotaltracker.com/story/show/75340328) for the launch, which could be an alternative for performing the proxying.

[itamarst]

We decided to go with docs.clusterhq.com on readthedocs. If that turns out to be a problem we can reopen this, otherwise we're all set.