headers
Ogoshi | 1 Dec 2007 01:26
Picon

Problem with gallery and cherokee

Hi.

I need help because for me is impossible to install gallery 2 with cherokee.

I explain all process that I use for install gallery

The first, the "document root" of cherokee is in /usr/var/www this is the standard directory to install
cherokee document root.(using
GNU/Debian Testing)

I make in document root a directory "gallery2" and "chmod 777". 
Next copy all files of gallery2.2.3-typical.zip in the directory.
Begin the install of gallery. The first step of gallery ok. I select the language of gallery. Push "Begin the installation".

Next "gallery checked" my system. All ok. Push "Next Step" and arrive on the "step" that you select "the type
of installation".

In this pages only have to options:
 - standard installation
 - multisite installation

I select the "standard" (is default selection), and push next step. But no pass to next step. Another time to
see "select the installation
type". Select "Standard" and push "next step" but another time "select".

Always that select "standard installation", always return to same pages.

Where is the problem, because I dont have for resolved this problem.

For more information. In the config file of cherokee the "users" to use cherokee is comment "#" (nobody &
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ogoshi | 1 Dec 2007 22:53
Picon

Re: Problem with gallery and cherokee

On Sat, 01 Dec 2007 14:19:42 +0000
"A.D.F." <adefacc <at> tin.it> wrote:

Ok.

Is possible that the problem is with gallery.

Know I tryng to install other version of gallery2 (2.1.2) and the
problem is the same?

What version of gallery use the person how using cherokee???

I prove the version of gallery (2.1.2) with my
stable server (is the server on stay my web) and the problem is the
same.

In the stable server, I have a directory of the web in the root
(site/stable/gallery) and the problem is the same. Not pass the step 4.

The person who use gallery where install?, where stay the
directory of cherokee, how "permissions, rules" of directorys (cherokee,
gallery, etc..) have or use??

Is possible that the problem is with the permissions

Thans
--

-- 
http://vctrsnts.dyndns.org
"Hay 10 tipos de personas en este mundo."
"Las que saben binario y las que no."
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ogoshi | 2 Dec 2007 00:58
Picon

Re: Problem with gallery and cherokee

On Sat, 01 Dec 2007 23:31:37 +0000
"A.D.F." <adefacc <at> tin.it> wrote:

> Ogoshi wrote:
> > 
> > On Sat, 01 Dec 2007 14:19:42 +0000
> > "A.D.F." <adefacc <at> tin.it> wrote:
> > 
> > Ok.
> > 	.
> > 	.
> > 	.
> > Is possible that the problem is with the permissions
> 
> Maybe, try Apache then and tell us if it works or not.
> 
> > Thans
> 
> OT: please, try to improve your written english
>     (it is "terrible" :-)
> 
> 		Greetings.
> 

Ok.

Im trying with apache....

But the persons who work with cherokee and gallery where is the
directory (DocumentRoot) of cherokee?? and use "User www-data" and
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan de Konink | 2 Dec 2007 02:55
Picon
Picon
Favicon

Debugging a request/redir rewrite regex


I'm very annoyed by the behavior of Cherokee especially by its way to
frustrate sysops with not working rewrites. Is there a way to debug or
SEE where a rewrite goes to?

Stefan
Permalink | Reply | 2 comments |
headers
Stefan de Konink | 2 Dec 2007 04:20
Picon
Picon
Favicon

Bug CGI


I have 3 files in a cgi-bin directory. Two are identical, one is different.

test.py
test1.py, create_user.py

When create_user.py is accessed from the cgi-bin directory it is
transfered as plain text without being executed. test1.py is just ran.
If I move my create_user.py to another directory it is just executed as cgi.

Yes that is odd isn't it?

> vserver!default!directory!/vps!handler = common
> vserver!default!directory!/vps!document_root = /var/vps
> vserver!default!directory!/vps!handler!iocache = 0
> vserver!default!directory!/vps!auth = plain
> vserver!default!directory!/vps!auth!methods = basic
> vserver!default!directory!/vps!auth!realm = Geen Beveiliging
> vserver!default!directory!/vps!auth!passwdfile = /var/vps/.htpasswd
> vserver!default!directory!/vps!priority = 20
> 
> vserver!default!directory!/vps/cgi-bin!document_root = /var/vps/cgi-bin
> vserver!default!directory!/vps/cgi-bin!handler = cgi
> vserver!default!directory!/vps/cgi-bin!priority = 21
> 
> vserver!default!directory!/vps/admin!handler = common
> vserver!default!directory!/vps/admin!document_root = /var/vps/admin
> vserver!default!directory!/vps/admin!handler!iocache = 0
> vserver!default!directory!/vps/admin!auth = plain
> vserver!default!directory!/vps/admin!auth!methods = basic
(Continue reading)

Permalink | Reply | 502 comments |
headers
Stefan de Konink | 2 Dec 2007 04:27
Picon
Picon
Favicon

Re: Bug CGI


Stefan de Konink schreef:
> I have 3 files in a cgi-bin directory. Two are identical, one is different.
> 
> test.py
> test1.py, create_user.py
> 
> When create_user.py is accessed from the cgi-bin directory it is
> transfered as plain text without being executed. test1.py is just ran.
> If I move my create_user.py to another directory it is just executed as cgi.
> 
> Yes that is odd isn't it?

...I wanted to give up. BUT, I changed the priorities to 20,21 and 20,21
and now it works. That is odd.

Anyone has a sensible explanation for this?

Stefan

ps. On my wishlish for Sinterklaas (6 december, big Dutch party) is
still the ability to create an authentication template with relative
passwdfiles. Or something that you could apply a regex on a passwdfile.
Permalink | Reply | 502 comments |
headers
Stefan de Konink | 3 Dec 2007 01:49
Picon
Picon
Favicon

CGI Bug II


My would the output CGI output:

Status: 301 Moved Permanently
Location: http://www.yoursite.nl/

End up in a 500 Internal Server Error?

#!/usr/bin/env python
print 'Status: 301 Moved Permanently'
print 'Location: http://www.jouwsite.nl/'

Stefan
Permalink | Reply | 2 comments |
headers
Alvaro Lopez Ortega | 3 Dec 2007 02:52
Picon
Gravatar

Re: Debugging a request/redir rewrite regex

Stefan de Konink wrote, On 01/12/2007 20:55:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> I'm very annoyed by the behavior of Cherokee especially by its way to
> frustrate sysops with not working rewrites. Is there a way to debug or
> SEE where a rewrite goes to?

There are two kinds of redirections: internal and client redirections.

The best thing that you can do is to set the redirections by using client 
redirections and then, if you want them to be internal (hidden from the 
client: the browser URL would not change) just remove the "show" option.

There are a few examples about the Cherokee 0.5 configuration files format:
http://www.cherokee-project.com/doc/Redirections.html

Anyway, there is another trick that you could use in Cherokee 0.6-beta. The 
new tracing facility will be quite useful in this case. You will need to 
compile the server with the --enable-trace parameter, and then launch the 
server with the CHEROKEE_TRACE environment variable. For instance:

CHEROKEE_TRACE=all /usr/sbin/cherokee

to trace everything, or in the case you want only the redir info:

CHEROKEE_TRACE=redir /usr/sbin/cherokee

--

-- 
Greetings, alo.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Stefan de Konink | 3 Dec 2007 02:56
Picon
Picon
Favicon

Re: Debugging a request/redir rewrite regex


Alvaro Lopez Ortega schreef:
> The best thing that you can do is to set the redirections by using
> client redirections and then, if you want them to be internal (hidden
> from the client: the browser URL would not change) just remove the
> "show" option.
> 
> There are a few examples about the Cherokee 0.5 configuration files format:
> http://www.cherokee-project.com/doc/Redirections.html

I'm at the 0.6, so the only useful 'documentation' I currently fetch
from the qa directory.

> Anyway, there is another trick that you could use in Cherokee 0.6-beta.
> The new tracing facility will be quite useful in this case. You will
> need to compile the server with the --enable-trace parameter, and then
> launch the server with the CHEROKEE_TRACE environment variable. For
> instance:
> 
> CHEROKEE_TRACE=all /usr/sbin/cherokee
> 
> to trace everything, or in the case you want only the redir info:
> 
> CHEROKEE_TRACE=redir /usr/sbin/cherokee

Wowie! Will check that out :)

Stefan
Permalink | Reply | 0 comments |
headers
Alvaro Lopez Ortega | 3 Dec 2007 03:00
Picon
Gravatar

Re: Bug CGI

Stefan de Konink wrote, On 01/12/2007 22:20:

> I have 3 files in a cgi-bin directory. Two are identical, one is different.
> 
> test.py
> test1.py, create_user.py
>
> When create_user.py is accessed from the cgi-bin directory it is
> transfered as plain text without being executed. test1.py is just ran.
> If I move my create_user.py to another directory it is just executed as cgi.

Where are these files? /vps/cgi-bin? all of then?

--

-- 
Greetings, alo.
http://www.alobbs.com
Permalink | Reply | 1 comment |

Gmane