{"action":"created","issue":{"url":"https://api.github.com/repos/cockroachdb/docs/issues/87","repository_url":"https://api.github.com/repos/cockroachdb/docs","labels_url":"https://api.github.com/repos/cockroachdb/docs/issues/87/labels{/name}","comments_url":"https://api.github.com/repos/cockroachdb/docs/issues/87/comments","events_url":"https://api.github.com/repos/cockroachdb/docs/issues/87/events","html_url":"https://github.com/cockroachdb/docs/issues/87","id":138273054,"number":87,"title":"automated push to prod","user":{"login":"mjibson","id":41181,"avatar_url":"https://avatars.githubusercontent.com/u/41181?v=3","gravatar_id":"","url":"https://api.github.com/users/mjibson","html_url":"https://github.com/mjibson","followers_url":"https://api.github.com/users/mjibson/followers","following_url":"https://api.github.com/users/mjibson/following{/other_user}","gists_url":"https://api.github.com/users/mjibson/gists{/gist_id}","starred_url":"https://api.github.com/users/mjibson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjibson/subscriptions","organizations_url":"https://api.github.com/users/mjibson/orgs","repos_url":"https://api.github.com/users/mjibson/repos","events_url":"https://api.github.com/users/mjibson/events{/privacy}","received_events_url":"https://api.github.com/users/mjibson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-03T19:22:36Z","updated_at":"2016-03-03T20:04:36Z","closed_at":null,"body":"We need a way that anyone in our org can use to push docs to the production server. Need to consider that master might be used as a testing branch, so it may not always be suitable for pushing. We could instead use a `prod` branch or something that is auto-pushed, and we manually push to that when we're ready to deploy stuff. I'm not thrilled by that, but it works. Better ideas?"},"comment":{"url":"https://api.github.com/repos/cockroachdb/docs/issues/comments/191939775","html_url":"https://github.com/cockroachdb/docs/issues/87#issuecomment-191939775","issue_url":"https://api.github.com/repos/cockroachdb/docs/issues/87","id":191939775,"user":{"login":"mjibson","id":41181,"avatar_url":"https://avatars.githubusercontent.com/u/41181?v=3","gravatar_id":"","url":"https://api.github.com/users/mjibson","html_url":"https://github.com/mjibson","followers_url":"https://api.github.com/users/mjibson/followers","following_url":"https://api.github.com/users/mjibson/following{/other_user}","gists_url":"https://api.github.com/users/mjibson/gists{/gist_id}","starred_url":"https://api.github.com/users/mjibson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjibson/subscriptions","organizations_url":"https://api.github.com/users/mjibson/orgs","repos_url":"https://api.github.com/users/mjibson/repos","events_url":"https://api.github.com/users/mjibson/events{/privacy}","received_events_url":"https://api.github.com/users/mjibson/received_events","type":"User","site_admin":false},"created_at":"2016-03-03T20:04:36Z","updated_at":"2016-03-03T20:04:36Z","body":"Other ideas discussed with @jseldess: use `docs.cockroachlabs.com` and have github pages build it. This would require using CloudFlare because that's the only way (that I'm aware of) to have HTTPS on github pages with a CNAME. @mberhault thoughts? Doesn't have to be for the entire domain (although we may want to do that anyway for the CDN benefits)."}}