{"action":"created","issue":{"url":"https://api.github.com/repos/Unitech/pm2-deploy/issues/37","repository_url":"https://api.github.com/repos/Unitech/pm2-deploy","labels_url":"https://api.github.com/repos/Unitech/pm2-deploy/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/Unitech/pm2-deploy/issues/37/comments","events_url":"https://api.github.com/repos/Unitech/pm2-deploy/issues/37/events","html_url":"https://github.com/Unitech/pm2-deploy/issues/37","id":57392332,"number":37,"title":"Secrets in ecosystem.json","user":{"login":"dbburgess","id":763971,"avatar_url":"https://avatars3.githubusercontent.com/u/763971?v=3","gravatar_id":"","url":"https://api.github.com/users/dbburgess","html_url":"https://github.com/dbburgess","followers_url":"https://api.github.com/users/dbburgess/followers","following_url":"https://api.github.com/users/dbburgess/following{/other_user}","gists_url":"https://api.github.com/users/dbburgess/gists{/gist_id}","starred_url":"https://api.github.com/users/dbburgess/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dbburgess/subscriptions","organizations_url":"https://api.github.com/users/dbburgess/orgs","repos_url":"https://api.github.com/users/dbburgess/repos","events_url":"https://api.github.com/users/dbburgess/events{/privacy}","received_events_url":"https://api.github.com/users/dbburgess/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2015-02-11T23:10:21Z","updated_at":"2017-04-15T13:21:12Z","closed_at":null,"body":"I'm currently working on deployments with pm2, and so far I really like how it works. There is one thing I don't get though. Generally, you keep application secrets out of your source control (api keys, database passwords, etc), and inject them into the application with environment variables. Cool, that makes sense.\n\nThe ecosystem.json file is a nice way to define the application,environments and variables to go with each for deployments. However, when I run the deploy command, I get this error: `Configuration file ecosystem.json is missing. Action canceled.` I presume this is because my ecosystem.json file is not on the remote server, as I haven't committed it into git.\n\nHow is this reconciled? Am I missing something? Are most people just committing their ecosystem.js and not worrying about any potential security issues with their secrets being included, or is there another way to inject the ecosystem file into the remote system? It'd be nice if the deploy command just pushed the file up or something.\n"},"comment":{"url":"https://api.github.com/repos/Unitech/pm2-deploy/issues/comments/294292990","html_url":"https://github.com/Unitech/pm2-deploy/issues/37#issuecomment-294292990","issue_url":"https://api.github.com/repos/Unitech/pm2-deploy/issues/37","id":294292990,"user":{"login":"mbilokonsky","id":603525,"avatar_url":"https://avatars0.githubusercontent.com/u/603525?v=3","gravatar_id":"","url":"https://api.github.com/users/mbilokonsky","html_url":"https://github.com/mbilokonsky","followers_url":"https://api.github.com/users/mbilokonsky/followers","following_url":"https://api.github.com/users/mbilokonsky/following{/other_user}","gists_url":"https://api.github.com/users/mbilokonsky/gists{/gist_id}","starred_url":"https://api.github.com/users/mbilokonsky/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbilokonsky/subscriptions","organizations_url":"https://api.github.com/users/mbilokonsky/orgs","repos_url":"https://api.github.com/users/mbilokonsky/repos","events_url":"https://api.github.com/users/mbilokonsky/events{/privacy}","received_events_url":"https://api.github.com/users/mbilokonsky/received_events","type":"User","site_admin":false},"created_at":"2017-04-15T13:21:12Z","updated_at":"2017-04-15T13:21:12Z","body":"Honestly even environment variables aside, this means I have to commit a file to my repo with my server info...? This seems super weird to me, I think I am not gonna use it."}}
{"actor":{"display_login":"mbilokonsky"}}