On Wed, Aug 26, 2009 at 02:35:17PM +0100, Ian H. wrote:
oh an .htaccess file is wrong.
root /var/www/domain.com/htdocs;
}
location ~ .php$ {
try_files $uri $uri/ /index.php;
I should have mentioned that I’m on ubuntu and therefore nginx 0.5.33
! No try-files.
So I must either compile nginx on (unfamilar) ubuntu, or work round the
missing try-files.
I should have mentioned that I’m on ubuntu and therefore nginx 0.5.33 Â ! Â No
try-files.
So I must either compile nginx on (unfamilar) ubuntu, or work round the
missing try-files.
And i thought Debian Sid was slow keeping up to date with nginx
(latest is 0.7.61 [1]).
The source comes with a configure script, it’s (almost) as simple as
running it. Search the nginx wiki for the modules you want to
add/remove and pertinent configuration/installation and you should do
fine. If you run into trouble the Ubuntu forums are a vast source of
help.
If it’s in the Ubuntu repos, i recommend using “checkinstall” ([2]?)
instead of “make install”, that way you’ll end up with a .deb to
install, which makes things much more clean.
The source comes with a configure script, it’s (almost) as simple as
running it. Search the nginx wiki for the modules you want to
add/remove and pertinent configuration/installation and you should do
fine. If you run into trouble the Ubuntu forums are a vast source of
help.
I managed to configure it to debian default, and then make and make
install on a test machine. I rather suspect that is it now too late for
checkinstall, although it does exist.
Now to release it to the server. Is this right?
Move /usr/local/smin/nginx to the same place, owner root:root, chmod
755.
From /etc/nginx move the files koi-win, koi-utf, win-utf, mine.types,
and fastcgi_params (checking the last for possible edits) to the same
place, all owned root:root, chmod 644.
How to check this before I do the copies and mess up the other 7 sites
on the server?
If it’s in the Ubuntu repos, i recommend using “checkinstall” ([2]?)
instead of “make install”, that way you’ll end up with a .deb to
install, which makes things much more clean.
I installed your repository and public key, and the apt-get update gave
an error…
Looks like you’re trying to give apt my personal key rather than that of
the
PPA. The ID of the PPA is mentioned in the error (and is different from
the
one in your apt-key command).
That said, you don’t need to do any of this. It just makes apt-get
update
quieter (and might avoid a MITM attack, however unlikely).
That said, you don’t need to do any of this. It just makes apt-get update
quieter (and might avoid a MITM attack, however unlikely).
Jeff
Hi Jeff,
Thanks for the explanation. Perhaps the instructions could be clearer.
I clicked on the “read about installing” link to open the box and found
“Step 1: On the PPA’s overview page you’ll see the PPA’s OpenPGP key
id. It’ll look something like this: /1024/12345678/. Copy it, or make a
note of, the portion after the slash, e.g: /12345678/.”
so I clicked the “overview” link in that page, and used the key I found
there.
I suspect I should have used the “Build dependencies signing key” on the
original page.
Regards
Ian
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.