On Sunday 12 January 2014 21:27:23 nano wrote:
[..]
> Another presumption on my part, however, where is the nginx regex
> documentation? I cannot seem to find it or even what syntax nginx uses.
Nginx uses PCRE. The documentation should be available in your system:
$ man pcrepattern
$ man pcres
On Sun, Jan 12, 2014 at 09:27:23PM +1100, nano wrote:
> On 11/01/2014 2:34 AM, Francis Daly wrote:
> >>On 10/01/2014 8:36 PM, Francis Daly wrote:
> On 10/01/2014 7:58 AM, Francis Daly wrote:
Hi there,
> > location ^~ /phpmyadmin/ {
> > location ~ \.php$ {
> >>>
> >>>At this poin
On 11/01/2014 2:34 AM, Francis Daly wrote:
On Fri, Jan 10, 2014 at 10:37:50PM +1100, nano wrote:
On 10/01/2014 8:36 PM, Francis Daly wrote:
On Fri, Jan 10, 2014 at 02:07:34PM +1100, nano wrote:
On 10/01/2014 7:58 AM, Francis Daly wrote:
Hi there,
This mail is going to sound a bit negative.
On Fri, Jan 10, 2014 at 10:37:50PM +1100, nano wrote:
> On 10/01/2014 8:36 PM, Francis Daly wrote:
> >On Fri, Jan 10, 2014 at 02:07:34PM +1100, nano wrote:
> >>On 10/01/2014 7:58 AM, Francis Daly wrote:
Hi there,
This mail is going to sound a bit negative.
> >>> location ^~ /phpmyadmin/ {
> >>
On 10/01/2014 8:36 PM, Francis Daly wrote:
On Fri, Jan 10, 2014 at 02:07:34PM +1100, nano wrote:
On 10/01/2014 7:58 AM, Francis Daly wrote:
Per nginx logic, location 4 is used for every request for which it is the
"best match". It just happens that there are no such requests. It's the
administ
On 10/01/2014 7:58 AM, Francis Daly wrote:
The suggestion is along the lines of:
location ^~ /phpmyadmin/ {
location ~ \.php$ {
# config for php scripts to be fastcgi_pass'd elsewhere
}
# config for static files to be served directly
}
and then whatever other top-le
On Fri, Jan 10, 2014 at 02:07:34PM +1100, nano wrote:
> On 10/01/2014 7:58 AM, Francis Daly wrote:
Hi there,
just some quick responses to parts...
> It was my mistake assuming Apache logic[0] would be used.
Yes -- in general, in Apache, the configuration that applies to a request
can come from
On 10/01/2014 7:58 AM, Francis Daly wrote:
Hi there,
The nginx config follows its own logic, which may not match your previous
experiences. When you understand that, you'll have a much better chance
of knowing the configuration you are looking for.
I think this is very true in my case. I will
On Fri, Jan 10, 2014 at 12:51:24AM +1100, nano wrote:
> On 9/01/2014 11:57 PM, B.R. wrote:
> >On Thu, Jan 9, 2014 at 1:41 PM, nano wrote:
Hi there,
The nginx config follows its own logic, which may not match your previous
experiences. When you understand that, you'll have a much better chance
of
On 10/01/2014 4:13 AM, Jim Ohlstein wrote:
Hello,
On 1/9/14, 9:42 AM, nano wrote:
I have attempted several variations of this format[1] you recommend and
continue to produce a broken site; dialog to download
application/octet-stream from the main servername.com and a 'File not
found.' from htt
Hello,
On 1/9/14, 9:42 AM, nano wrote:
I have attempted several variations of this format[1] you recommend and
continue to produce a broken site; dialog to download
application/octet-stream from the main servername.com and a 'File not
found.' from https://servername.com/phpmyadmin.
[1]
locatio
On 9/01/2014 11:57 PM, B.R. wrote:
II. Use a smarter (and more scalable, in light of future adds to the
nginx config) way, which is nesting the rules of 'location
/phpmyadmin/(.*\.php)$' in a 'location ~\.php$' block embedded in a
'location ^~ /phpmyadmin/' block.
I have attempted several var
On 9/01/2014 11:57 PM, B.R. wrote:
Try to understand what you are doing first.
I really am trying.
One request is handled in one location.
For this request, the one location that you want to be used is
not the
one that nginx actually uses.
1.
Try to understand what you are doing first.
One request is handled in one location.
>>
>> For this request, the one location that you want to be used is not the
>> one that nginx actually uses.
>>
>>
>>> 1.
>>> location / {
>>>
>>> 2.
>>> location ~ \.php$ {
>>>
>>> 3.
>>> location /php
On 9/01/2014 9:23 PM, nano wrote:
I am having trouble configuring nginx to serve up PHP from outside of
the server document root. For example, this site's root is
/usr/local/www/site1/wordpress and phpMyAdmin is located in
/usr/local/www/phpMyAdmin. I cannot access servername.com/phpmyadmin.
ngin
On 9/01/2014 9:55 PM, Francis Daly wrote:
On Thu, Jan 09, 2014 at 09:23:56PM +1100, nano wrote:
Hi there,
One request is handled in one location.
For this request, the one location that you want to be used is not the
one that nginx actually uses.
location / {
location ~ \.p
On Thu, Jan 09, 2014 at 09:23:56PM +1100, nano wrote:
Hi there,
> The WordPress site, however, is served without error. Therefore, nginx
> is refusing to serve PHP from outside of the server document root.
nginx doesn't serve php.
nginx tells the fastcgi server what you configure it to tell.
On 9/01/2014 9:27 PM, Richard Stanway wrote:
fastcgi_passunix:/tmp/php-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME
/usr/local/www/phpMyAdmin$fastcgi_script_name;
include fastcgi_params;
What's in your fastcgi_para
> fastcgi_passunix:/tmp/php-fpm.sock;
> fastcgi_index index.php;
> fastcgi_param SCRIPT_FILENAME
> /usr/local/www/phpMyAdmin$fastcgi_script_name;
> include fastcgi_params;
>
What's in your fastcgi_params? Is it overriding your SCRIPT_FILENAME
I am having trouble configuring nginx to serve up PHP from outside of
the server document root. For example, this site's root is
/usr/local/www/site1/wordpress and phpMyAdmin is located in
/usr/local/www/phpMyAdmin. I cannot access servername.com/phpmyadmin.
nginx logs the following error:
==
20 matches
Mail list logo
