Re: Question

Anyone else running ngxin willing to review this? Otherwise I imagine I can add it as-is -Hannes On Fri, Feb 27, 2015 at 2:01 AM, Silasi Stefan <silasistefan@gmail.com> wrote: > Hello, > > Not sure if this is the right place to post this, but here's the nginx > configuration from ro1.php.net, CNAME to php.spidervps.com. Change the > config to match your IP, hostname, mirror name and path. > > server { > listen 188.241.113.74:80; > server_name ro1.php.net php.spidervps.com ro.php.net php.net www.php.net > ; > access_log /var/log/nginx/php.spidervps.com.log main; > > location / { > root /home/php.spidervps.com/; > index index.html index.htm index.php; > expires max; > error_page 401 402 403 404 = /error.php; > } > > location ~\.php$ { > root /home/php.spidervps.com/; > fastcgi_pass unix:///var/run/php.sock; > fastcgi_index index.php; > fastcgi_param SCRIPT_FILENAME /home/ > php.spidervps.com/$fastcgi_script_name; > fastcgi_param QUERY_STRING $query_string; > fastcgi_param REQUEST_METHOD $request_method; > fastcgi_param CONTENT_TYPE $content_type; > fastcgi_param CONTENT_LENGTH $content_length; > fastcgi_param GATEWAY_INTERFACE CGI/1.1; > fastcgi_param SERVER_SOFTWARE nginx; > fastcgi_param SCRIPT_NAME > $fastcgi_script_name; > fastcgi_param REQUEST_URI $request_uri; > fastcgi_param DOCUMENT_URI $document_uri; > fastcgi_param DOCUMENT_ROOT $document_root; > fastcgi_param SERVER_PROTOCOL $server_protocol; > fastcgi_param REMOTE_ADDR $remote_addr; > fastcgi_param REMOTE_PORT $remote_port; > fastcgi_param SERVER_ADDR $server_addr; > fastcgi_param SERVER_PORT $server_port; > fastcgi_param SERVER_NAME "ro1.php.net"; > expires off; > fastcgi_intercept_errors on; > } > } > > This is running for more than a year now. Please let me know if you have > any questions. > > Cheers, > Stefan. > > On Fri, Feb 27, 2015 at 9:57 AM, Oskar Szafraniec < > oskar.szafraniec@webdev.pl> wrote: > >> OK, so do it :) php.net is just a php website, nothing fancy, any >> webserver with php support can handle it :) And if you will do it, write a >> tutorial how you did it, they will likely add it to the mirror page for >> everyone to know it :) And you will be famous ;) >> >> Z pozdrowieniami >> Oskar Szafraniec >> >> >> >> > Wiadomość napisana przez Karol Chmurzyński <info@chmuri..net> w dniu 27 >> lut 2015, o godz. 10:38: >> > >> > Yes but my mirror.chmuri.net use nginx as default so its would be nice >> to run it as one webserver and use only 80 port in security;) >> > >> > On 2015-02-27 10:03, Oskar Szafraniec wrote: >> >> Nginx is not a bad idea, but I don’t see why Apache is bad for it. We >> are running pl1.php.net <http://pl1.php.net> mirror >> and the traffic is >> not so big to run it on nginx. We use Apache. I don’t see any advantage >> here for switching to nginx. Main php.net >> <http://php.net> OK, there is >> some high traffic there, but for a mirror… You can stay with Apache without >> a problem :) >> >> >> >> I think it’s only a matter of taste and… de gustibus non est >> disputandum ;) >> >> >> >> Regards / Z pozdrowieniami >> >> Oskar Szafraniec >> >> / >> >> / >> >> >> >>> Wiadomość napisana przez Pål Sollie <sollie@sparkz.no <mailto: >> sollie@sparkz.no>> w dniu 27 lut 2015, o godz. 09:23: >> >>> >> >>> On 27.02.15, 09.07, Kaspars Foigts wrote: >> >>>> Maybe it would be nice to add nginx configuration to mirroring page? I >> >>>> believe many would like to move to nginx, though text on mirroring >> page >> >>>> <http://lv.php.net/mirroring.php> is >> >>>> a little bit discouraging: >> >>>> >> >>>> NOTE: Some of our maintainers prefer to use web servers other than >> >>>> Apache, such as Nginx. While this is permitted (as long as >> >>>> everything ultimately works as directed), we do not officially >> >>>> support these setups at this time >> >>> >> >>> I suspect that part of the documentation is a bit dated. I think the >> >>> main site has been running nginx for a couple of years now so it hardly >> >>> makes sense to discourage it for mirrors. >> >>> >> >>> -- >> >>> Pål Sollie >> >>> sollie@sparkz.no >> >>> <mailto:sollie@sparkz.no> >> >> >> > >> >>