{"action":"created","issue":{"url":"https://api.github.com/repos/pyupio/statuspage/issues/5","repository_url":"https://api.github.com/repos/pyupio/statuspage","labels_url":"https://api.github.com/repos/pyupio/statuspage/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/pyupio/statuspage/issues/5/comments","events_url":"https://api.github.com/repos/pyupio/statuspage/issues/5/events","html_url":"https://github.com/pyupio/statuspage/issues/5","id":138991543,"number":5,"title":"Automated builds based on travis","user":{"login":"captn3m0","id":584253,"avatar_url":"https://avatars.githubusercontent.com/u/584253?v=3","gravatar_id":"","url":"https://api.github.com/users/captn3m0","html_url":"https://github.com/captn3m0","followers_url":"https://api.github.com/users/captn3m0/followers","following_url":"https://api.github.com/users/captn3m0/following{/other_user}","gists_url":"https://api.github.com/users/captn3m0/gists{/gist_id}","starred_url":"https://api.github.com/users/captn3m0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/captn3m0/subscriptions","organizations_url":"https://api.github.com/users/captn3m0/orgs","repos_url":"https://api.github.com/users/captn3m0/repos","events_url":"https://api.github.com/users/captn3m0/events{/privacy}","received_events_url":"https://api.github.com/users/captn3m0/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-03-07T14:26:25Z","updated_at":"2016-03-08T16:25:32Z","closed_at":null,"body":"Love the idea and project. I was wondering if it makes sense to move the build/deploy process to travis instead? I do the same at [hackercouch](https://github.com/hackercouch/hackercouch/blob/master/_script/deploy.sh) and it currently runs the deploy on every commit to master.\r\n\r\nIn order to keep it updated, we also use nightli.es as a backup. Thinking if would be possible to pipe the github event for issues.* on the repo to trigger a build in travis."},"comment":{"url":"https://api.github.com/repos/pyupio/statuspage/issues/comments/193848994","html_url":"https://github.com/pyupio/statuspage/issues/5#issuecomment-193848994","issue_url":"https://api.github.com/repos/pyupio/statuspage/issues/5","id":193848994,"user":{"login":"manavo","id":259487,"avatar_url":"https://avatars.githubusercontent.com/u/259487?v=3","gravatar_id":"","url":"https://api.github.com/users/manavo","html_url":"https://github.com/manavo","followers_url":"https://api.github.com/users/manavo/followers","following_url":"https://api.github.com/users/manavo/following{/other_user}","gists_url":"https://api.github.com/users/manavo/gists{/gist_id}","starred_url":"https://api.github.com/users/manavo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/manavo/subscriptions","organizations_url":"https://api.github.com/users/manavo/orgs","repos_url":"https://api.github.com/users/manavo/repos","events_url":"https://api.github.com/users/manavo/events{/privacy}","received_events_url":"https://api.github.com/users/manavo/received_events","type":"User","site_admin":false},"created_at":"2016-03-08T16:25:32Z","updated_at":"2016-03-08T16:25:32Z","body":"It would obviously be a big change to the project, but theoretically the template/page could get built on the front-end, to avoid needing a re-build each time? It seems you can read issues via the API without auth: https://api.github.com/repos/pyupio/statuspage/issues\r\n\r\nThat way you would only need a rebuild if adding a new system or something?\r\n\r\n(just thinking out loud, sorry if too off topic for the original issue)"}}