{"action":"created","issue":{"url":"https://api.github.com/repos/HaxeFoundation/haxe.org/issues/41","labels_url":"https://api.github.com/repos/HaxeFoundation/haxe.org/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/HaxeFoundation/haxe.org/issues/41/comments","events_url":"https://api.github.com/repos/HaxeFoundation/haxe.org/issues/41/events","html_url":"https://github.com/HaxeFoundation/haxe.org/issues/41","id":34537294,"number":41,"title":"Github automation for Haxe website","user":{"login":"jasononeil","id":315158,"avatar_url":"https://avatars.githubusercontent.com/u/315158?v=3","gravatar_id":"","url":"https://api.github.com/users/jasononeil","html_url":"https://github.com/jasononeil","followers_url":"https://api.github.com/users/jasononeil/followers","following_url":"https://api.github.com/users/jasononeil/following{/other_user}","gists_url":"https://api.github.com/users/jasononeil/gists{/gist_id}","starred_url":"https://api.github.com/users/jasononeil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasononeil/subscriptions","organizations_url":"https://api.github.com/users/jasononeil/orgs","repos_url":"https://api.github.com/users/jasononeil/repos","events_url":"https://api.github.com/users/jasononeil/events{/privacy}","received_events_url":"https://api.github.com/users/jasononeil/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2014-05-29T08:32:13Z","updated_at":"2015-02-28T10:38:52Z","closed_at":"2015-02-23T22:45:49Z","body":"I'd like to work on this over the weekend, but have a few questions re: strategy.\r\n\r\nWith the manual, we have a Github hook set up so any \"push\" event will get the site to pull down the latest markdown content, convert it to HTML, and keep a copy for any requests to `/manual/*`\r\n\r\nFor the site, I do not want to fully automate this, as we have a mix of content and code/design - sometimes we may want to merge a pull request but preview it before going live.\r\n\r\nI propose:\r\n\r\n* Having two branches, \"master\" and \"staging\".\r\n* Any pull requests which are simple content changes go to \"master\"\r\n* Any pull requests which involve changing code or stylesheets go to \"staging\"\r\n* Github links \"master\" with the live site, so a push/merge on master will trigger an update of the live site.\r\n* Github links \"staging\" with `staging.haxe.org` (or similar) and we can preview changes there after a push/merge to the staging branch.\r\n* If we like what we see on staging, we merge into master.\r\n\r\nDoes this sound like an acceptable workflow?\r\n\r\ncc @ncannasse @Simn "},"comment":{"url":"https://api.github.com/repos/HaxeFoundation/haxe.org/issues/comments/76520858","html_url":"https://github.com/HaxeFoundation/haxe.org/issues/41#issuecomment-76520858","issue_url":"https://api.github.com/repos/HaxeFoundation/haxe.org/issues/41","id":76520858,"user":{"login":"jasononeil","id":315158,"avatar_url":"https://avatars.githubusercontent.com/u/315158?v=3","gravatar_id":"","url":"https://api.github.com/users/jasononeil","html_url":"https://github.com/jasononeil","followers_url":"https://api.github.com/users/jasononeil/followers","following_url":"https://api.github.com/users/jasononeil/following{/other_user}","gists_url":"https://api.github.com/users/jasononeil/gists{/gist_id}","starred_url":"https://api.github.com/users/jasononeil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasononeil/subscriptions","organizations_url":"https://api.github.com/users/jasononeil/orgs","repos_url":"https://api.github.com/users/jasononeil/repos","events_url":"https://api.github.com/users/jasononeil/events{/privacy}","received_events_url":"https://api.github.com/users/jasononeil/received_events","type":"User","site_admin":false},"created_at":"2015-02-28T10:38:52Z","updated_at":"2015-02-28T10:38:52Z","body":"Yeah for sure - can you create a new issue and assign it to me?\n\nBasically the process will be:\n\n   - Generate a RSA key, and encrypt it in a way that Travis can decrypt.\n   I followed the instructions here:\n\n\n   http://pghalliday.com/github/ssh/travis-ci/2014/09/19/auto-build-and-deploy-github-pages-with-travis-ci.html\n\n   though I think I simplified it a little bit.\n\n   - Make sure that key is in the \"authorized_keys\" on the haxe.org server\n   for a user that has permission to write to that directory.\n\n\n   - In Travis, add something like:\n\n   scp bin/api.zip user@haxe.org/data/api-dir/api.zip\n   ssh user@haxe.org \"linux command to unzip to the right location\"\n\nIt will be great to have the dev version be that current.\n\nOn Wed, Feb 25, 2015 at 7:28 PM, Simon Krajewski <notifications@github.com>\nwrote:\n\n> @jasononeil <https://github.com/jasononeil>: I just checked the\n> deployment through travis, it's really nice!\n>\n> Do you think you could help getting the same done for our API docs? Our\n> travis already builds a .zip from with the latest documentation here:\n> https://travis-ci.org/HaxeFoundation/haxe/jobs/52106094#L618\n>\n> The idea is to automatically sync that to http://api.haxe.org/v/dev/ so\n> we always have the latest documentation there. I was briefly talking with\n> @andyli <https://github.com/andyli> about it but never got around to\n> figuring out how to setup the SSH access properly.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/HaxeFoundation/haxe.org/issues/41#issuecomment-75945169>\n> .\n>\n"}}