{"action":"opened","issue":{"url":"https://api.github.com/repos/crushlovely/ansible-unicorn-upstart/issues/2","labels_url":"https://api.github.com/repos/crushlovely/ansible-unicorn-upstart/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/crushlovely/ansible-unicorn-upstart/issues/2/comments","events_url":"https://api.github.com/repos/crushlovely/ansible-unicorn-upstart/issues/2/events","html_url":"https://github.com/crushlovely/ansible-unicorn-upstart/issues/2","id":68998848,"number":2,"title":"Variable naming ","user":{"login":"pablitoc","id":5421590,"avatar_url":"https://avatars.githubusercontent.com/u/5421590?v=3","gravatar_id":"","url":"https://api.github.com/users/pablitoc","html_url":"https://github.com/pablitoc","followers_url":"https://api.github.com/users/pablitoc/followers","following_url":"https://api.github.com/users/pablitoc/following{/other_user}","gists_url":"https://api.github.com/users/pablitoc/gists{/gist_id}","starred_url":"https://api.github.com/users/pablitoc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pablitoc/subscriptions","organizations_url":"https://api.github.com/users/pablitoc/orgs","repos_url":"https://api.github.com/users/pablitoc/repos","events_url":"https://api.github.com/users/pablitoc/events{/privacy}","received_events_url":"https://api.github.com/users/pablitoc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-16T20:01:21Z","updated_at":"2015-04-16T20:01:21Z","closed_at":null,"body":"@pjkelly - Flagging this as an issue to allow us some more time to think about.\r\n in general, this and the sidekiq roles look good. I have to call into question the variable naming though - these roles are making some general assumptions about how you configure your playbooks (with app_name, app_path, etc.), so I think explanation is warranted in the Readme about why it's setup this way. Thinking more long-term, having a general write-up on your variable strategy across roles and how it all fits together in the context of provisioning an application would be really nice to have.\r\n\r\nThe alternative here would be changing the variables in these two roles so they're a little more generic. e.g.\r\n```\r\nsidekiq:\r\n  conf_file: [full filename goes here]\r\n  app_path: [full path goes here]\r\n...\r\n\r\nunicorn:\r\n  conf_file: [full filename goes here]\r\n  app_path: [full path goes here]\r\n```\r\nNot saying you need to change your approach - just offering food for thought as someone who might want to use this role but doesn't understand the general strategy you're using."}}