I need to make a couple changes to the init script
1. The current release of nginx (0.8.20) has changed the location of the PID file, causing the script http://gist.github.com/54030 to fail. Simply modify it as follows:
2. The script also uses WIN/MAC style CRLF, which makes /bin/sh complain on Linux. Run dos2unix on the file would fix that.
Gordon, 2010/02/07 23:57
hi there,
“Configure Nginx to talk to Thin” –> Can you please let us know where to save this file to?
thank you :)
Josue Camara Fernandez, 2011/07/01 21:26
Hello.
I'm using ruby 1.8.7, rugygems 1.8.5, Rails 3.0.9, nginx 1.0.4 and thin 1.2.11, I have followed all the steps as indicated and make it work achieving my amazon ec2 server.
Discussion
I need to make a couple changes to the init script
1. The current release of nginx (0.8.20) has changed the location of the PID file, causing the script http://gist.github.com/54030 to fail. Simply modify it as follows:
<pre>
+ NGINXHOME=/usr/local/nginx
! CONFIGFILE=$NGINXHOME/conf/nginx.conf ! PIDFILE=$NGINXHOME/logs/$NAME.pid
</pre>
2. The script also uses WIN/MAC style CRLF, which makes /bin/sh complain on Linux. Run dos2unix on the file would fix that.
hi there,
“Configure Nginx to talk to Thin” –> Can you please let us know where to save this file to?
thank you :)
Hello.
I'm using ruby 1.8.7, rugygems 1.8.5, Rails 3.0.9, nginx 1.0.4 and thin 1.2.11, I have followed all the steps as indicated and make it work achieving my amazon ec2 server.
quad access my server like this: http://servidor:3000/ I get the message:
“We're sorry, But Something Went Wrong. We've Been Notified about this issue and we'll take a look at it Shortly. ”
Does anyone have an idea of what happens? Greetings.