{"action":"created","issue":{"url":"https://api.github.com/repos/WGBH/AAPB2/issues/380","labels_url":"https://api.github.com/repos/WGBH/AAPB2/issues/380/labels{/name}","comments_url":"https://api.github.com/repos/WGBH/AAPB2/issues/380/comments","events_url":"https://api.github.com/repos/WGBH/AAPB2/issues/380/events","html_url":"https://github.com/WGBH/AAPB2/issues/380","id":73332475,"number":380,"title":"get ci.yml to stick after redeploys","user":{"login":"mccalluc","id":730388,"avatar_url":"https://avatars.githubusercontent.com/u/730388?v=3","gravatar_id":"","url":"https://api.github.com/users/mccalluc","html_url":"https://github.com/mccalluc","followers_url":"https://api.github.com/users/mccalluc/followers","following_url":"https://api.github.com/users/mccalluc/following{/other_user}","gists_url":"https://api.github.com/users/mccalluc/gists{/gist_id}","starred_url":"https://api.github.com/users/mccalluc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mccalluc/subscriptions","organizations_url":"https://api.github.com/users/mccalluc/orgs","repos_url":"https://api.github.com/users/mccalluc/repos","events_url":"https://api.github.com/users/mccalluc/events{/privacy}","received_events_url":"https://api.github.com/users/mccalluc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-05-05T14:35:39Z","updated_at":"2015-05-06T19:21:33Z","closed_at":null,"body":"@afred : Thoughts on ci.yml?\r\n- Let it be shared across deployments. (After it is put in place by hand once.)\r\n- or, put it in place as part of the deployment process.\r\n- or, ...?"},"comment":{"url":"https://api.github.com/repos/WGBH/AAPB2/issues/comments/99579446","html_url":"https://github.com/WGBH/AAPB2/issues/380#issuecomment-99579446","issue_url":"https://api.github.com/repos/WGBH/AAPB2/issues/380","id":99579446,"user":{"login":"afred","id":1507490,"avatar_url":"https://avatars.githubusercontent.com/u/1507490?v=3","gravatar_id":"","url":"https://api.github.com/users/afred","html_url":"https://github.com/afred","followers_url":"https://api.github.com/users/afred/followers","following_url":"https://api.github.com/users/afred/following{/other_user}","gists_url":"https://api.github.com/users/afred/gists{/gist_id}","starred_url":"https://api.github.com/users/afred/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/afred/subscriptions","organizations_url":"https://api.github.com/users/afred/orgs","repos_url":"https://api.github.com/users/afred/repos","events_url":"https://api.github.com/users/afred/events{/privacy}","received_events_url":"https://api.github.com/users/afred/received_events","type":"User","site_admin":false},"created_at":"2015-05-06T19:21:33Z","updated_at":"2015-05-06T19:21:33Z","body":"Yes\r\n\r\nPart of the deployment process should include being able to set the things that are shared between deployments.\r\n\r\nI'm leaning toward a a set of cap recipes such as `deploy:ci_config`, `deploy:db_config`, `deploy:app_secret`, `deploy:redis_config`. The goal being to put sensitive data (secrets and config) into their appropriate location on production servers. Most often that location is the \"shared\" directory that is shared across deployments.\r\n\r\nThe sensitive data could come from a protected repository (e.g. Stash). Or we could have capistrano prompt the user at runtime. Or read from a local file. Whatever makes the most sense."}}