[00:18] <lactose>  so i am trying to set up rails with unicorn. i have my unicorn 
[00:18] <lactose>                  config.rb file set up, and if i run unicorn_rails -c 
[00:18] <lactose>                  /path/to/config.rb as my user everything starts up fine and i 
[00:18] <lactose> woops
[00:19] <lactose> so i am trying to set up rails with unicorn.  i have my unicorn config.rb file set up, and if i run unciorn_rails -c /path/to/config.rb as my user everything starts up fine and i can view the website. however ifi run the Upstart script, I get no error message, (and the script basically exec sudo -u myuser -i `unicorn_rails -c 'path/to/config'` but i cant view the website. im redirected to my 500 error page (in the logs it says 111 con
[00:32] <SpamapS> lactose: probably something in your environment that is needed. Maybe try adding > /var/log/myjob.log 2>&1 to see if there are helpful errors.
[00:32]  * SpamapS disappears
[00:36] <lactose> SpamapS: I have done so, and the file is empty
[00:37] <lactose> SpamapS: do yo uthink that the unicorn_rails command cannot be accessed -- my ruby install is through rvm and I personally cannot run this command unless I am in the working directory. But if this were the case, why is the error log file blank?
[00:51] <lactose> SpamapS: this was the problem. I chowned the .conf file in /etc/init to myuser and transferred the command to .sh in the directory of the rails app, then the conf simply exec the .sh. Do you see any security or other problem with this approach? 
[00:51] <lactose> anybody else can answer that as well
[07:22] <SpamapS> lactose: you shouldn't need to chown the upstart job to your user.. that should not change who the job runs as.
=== ion_ is now known as ion