{"issue":{"state":"open","pull_request":{"diff_url":"https://github.com/fuel/fuel/pull/254.diff","html_url":"https://github.com/fuel/fuel/pull/254","patch_url":"https://github.com/fuel/fuel/pull/254.patch"},"user":{"avatar_url":"https://secure.gravatar.com/avatar/033216e8f58f49c4e1ac20744b70bc38?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"033216e8f58f49c4e1ac20744b70bc38","url":"https://api.github.com/users/fabioluciano","login":"fabioluciano","id":499057},"milestone":null,"updated_at":"2011-11-06T03:07:54Z","labels":[],"assignee":null,"closed_at":null,"comments":3,"url":"https://api.github.com/repos/fuel/fuel/issues/254","body":"When you need to put a oil refine to a cronjob you need to put the full path of oil executable. But, the script doesnt \"know\" how to execute it. I added the \"#!/usr/bin/php\", in the file to get this fixed.","html_url":"https://github.com/fuel/fuel/issues/254","number":254,"title":"Adding the full path to php in oil executable","id":2153875,"created_at":"2011-11-05T22:04:06Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/033216e8f58f49c4e1ac20744b70bc38?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"033216e8f58f49c4e1ac20744b70bc38","url":"https://api.github.com/users/fabioluciano","login":"fabioluciano","id":499057},"updated_at":"2011-11-06T03:07:54Z","url":"https://api.github.com/repos/fuel/fuel/issues/comments/2643702","body":"Yes, oil is a php file. But in the context of command line, doesn't. If you don't use the shebang, to specify the interpreter, it doesn't make sense. Do you agree?\r\n\r\nIf the file is a php file, why not use shebang to specify it? Is just a question of security of which interpreter will be in use.","id":2643702,"created_at":"2011-11-06T03:07:54Z"}}