Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cherokee: users

new to cherokee

 

 

Cherokee users RSS feed   Index | Next | Previous | View Threaded


mp3geek at gmail

May 8, 2011, 7:07 AM

Post #1 of 15 (1014 views)
Permalink
new to cherokee

Installing from a tarball and compiled, but when I start it
"/etc/init.d/cherokee start", no cherokee log files in /var/log/

root [at] server:/etc/init.d# ./cherokee start
Starting cherokee web server: cherokee.
root [at] server:/etc/init.d# ps aux | grep chero
root 13513 0.0 0.2 1876 596 pts/0 S+ 18:04 0:00 grep
--color=auto chero
root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
##
## cherokee.conf -- Cherokee HTTP server configuration file
##
## Common use
##
## NOTE: This file is NOT meant to be edited by hand. Instead, a
## convenient configuration interface is available, so the server can
## be tweaked in a easy and safe way. Run cherokee-admin as root, and
## then proceed to point your web browser to: http://localhost:9090/
##

# Server
#
server!bind!1!port = 80
server!timeout = 15
server!keepalive = 1
server!keepalive_max_requests = 500
server!server_tokens = full
server!panic_action = /usr/local/bin/cherokee-panic
server!pid_file = /var/run/cherokee.pid

# Default virtual server
#
vserver!1!nick = default
vserver!1!document_root = /var/www
vserver!1!directory_index = index.html

vserver!1!logger = combined
vserver!1!logger!access!type = file
vserver!1!logger!access!filename = /var/log/cherokee.access
vserver!1!logger!access!buffsize = 16384

vserver!1!error_writer!type = file
vserver!1!error_writer!filename = /var/log/cherokee.error

vserver!1!rule!1!match = default
vserver!1!rule!1!handler = common
vserver!1!rule!1!handler!iocache = 1

vserver!1!rule!2!match = directory
vserver!1!rule!2!match!directory = /icons
vserver!1!rule!2!handler = file
vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons

vserver!1!rule!3!match = directory
vserver!1!rule!3!match!directory = /cherokee_themes
vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
vserver!1!rule!3!handler = file

vserver!1!rule!4!match = directory
vserver!1!rule!4!match!directory = /cgi-bin
vserver!1!rule!4!document_root = NONE/lib/cgi-bin
vserver!1!rule!4!handler = cgi

vserver!1!rule!5!match = directory
vserver!1!rule!5!match!directory = /about
vserver!1!rule!5!encoder!gzip = 1
vserver!1!rule!5!handler = server_info
vserver!1!rule!5!handler!type = just_about
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


me at pigmej

May 8, 2011, 7:12 AM

Post #2 of 15 (988 views)
Permalink
Re: new to cherokee [In reply to]

If you're new:

## be tweaked in a easy and safe way. Run cherokee-admin as root, and
## then proceed to point your web browser to: http://localhost:9090/

You should read that lines in .conf ;)

Just run cherokee-admin ;)

Greetings,
Jędrzej Nowak



On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
> Installing from a tarball and compiled, but when I start it
> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>
> root [at] server:/etc/init.d# ./cherokee start
> Starting cherokee web server: cherokee.
> root [at] server:/etc/init.d# ps aux | grep chero
> root     13513  0.0  0.2   1876   596 pts/0    S+   18:04   0:00 grep
> --color=auto chero
> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
> ##
> ## cherokee.conf -- Cherokee HTTP server configuration file
> ##
> ## Common use
> ##
> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
> ## convenient configuration interface is available, so the server can
> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
> ## then proceed to point your web browser to: http://localhost:9090/
> ##
>
> # Server
> #
> server!bind!1!port = 80
> server!timeout = 15
> server!keepalive = 1
> server!keepalive_max_requests = 500
> server!server_tokens = full
> server!panic_action = /usr/local/bin/cherokee-panic
> server!pid_file = /var/run/cherokee.pid
>
> # Default virtual server
> #
> vserver!1!nick = default
> vserver!1!document_root = /var/www
> vserver!1!directory_index = index.html
>
> vserver!1!logger = combined
> vserver!1!logger!access!type = file
> vserver!1!logger!access!filename = /var/log/cherokee.access
> vserver!1!logger!access!buffsize = 16384
>
> vserver!1!error_writer!type = file
> vserver!1!error_writer!filename = /var/log/cherokee.error
>
> vserver!1!rule!1!match = default
> vserver!1!rule!1!handler = common
> vserver!1!rule!1!handler!iocache = 1
>
> vserver!1!rule!2!match = directory
> vserver!1!rule!2!match!directory = /icons
> vserver!1!rule!2!handler = file
> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>
> vserver!1!rule!3!match = directory
> vserver!1!rule!3!match!directory = /cherokee_themes
> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
> vserver!1!rule!3!handler = file
>
> vserver!1!rule!4!match = directory
> vserver!1!rule!4!match!directory = /cgi-bin
> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
> vserver!1!rule!4!handler = cgi
>
> vserver!1!rule!5!match = directory
> vserver!1!rule!5!match!directory = /about
> vserver!1!rule!5!encoder!gzip = 1
> vserver!1!rule!5!handler = server_info
> vserver!1!rule!5!handler!type = just_about
> _______________________________________________
> Cherokee mailing list
> Cherokee [at] lists
> http://lists.octality.com/listinfo/cherokee
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


mp3geek at gmail

May 8, 2011, 7:25 AM

Post #3 of 15 (990 views)
Permalink
Re: new to cherokee [In reply to]

Ah, but I did :)

root [at] server:~# lynx http://localhost:9090

Looking up localhost:9090
Making HTTP connection to localhost:9090
Alert!: Unable to connect to remote host.

lynx: Can't access startfile http://localhost:9090/

Nothing is showing in ps, so it's not surprising lynx can't load it


2011/5/9 Jędrzej Nowak <me [at] pigmej>:
> If you're new:
>
> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
> ## then proceed to point your web browser to: http://localhost:9090/
>
> You should read that lines in .conf ;)
>
> Just run cherokee-admin ;)
>
> Greetings,
> Jędrzej Nowak
>
>
>
> On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
>> Installing from a tarball and compiled, but when I start it
>> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>>
>> root [at] server:/etc/init.d# ./cherokee start
>> Starting cherokee web server: cherokee.
>> root [at] server:/etc/init.d# ps aux | grep chero
>> root     13513  0.0  0.2   1876   596 pts/0    S+   18:04   0:00 grep
>> --color=auto chero
>> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
>> ##
>> ## cherokee.conf -- Cherokee HTTP server configuration file
>> ##
>> ## Common use
>> ##
>> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
>> ## convenient configuration interface is available, so the server can
>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>> ## then proceed to point your web browser to: http://localhost:9090/
>> ##
>>
>> # Server
>> #
>> server!bind!1!port = 80
>> server!timeout = 15
>> server!keepalive = 1
>> server!keepalive_max_requests = 500
>> server!server_tokens = full
>> server!panic_action = /usr/local/bin/cherokee-panic
>> server!pid_file = /var/run/cherokee.pid
>>
>> # Default virtual server
>> #
>> vserver!1!nick = default
>> vserver!1!document_root = /var/www
>> vserver!1!directory_index = index.html
>>
>> vserver!1!logger = combined
>> vserver!1!logger!access!type = file
>> vserver!1!logger!access!filename = /var/log/cherokee.access
>> vserver!1!logger!access!buffsize = 16384
>>
>> vserver!1!error_writer!type = file
>> vserver!1!error_writer!filename = /var/log/cherokee.error
>>
>> vserver!1!rule!1!match = default
>> vserver!1!rule!1!handler = common
>> vserver!1!rule!1!handler!iocache = 1
>>
>> vserver!1!rule!2!match = directory
>> vserver!1!rule!2!match!directory = /icons
>> vserver!1!rule!2!handler = file
>> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>>
>> vserver!1!rule!3!match = directory
>> vserver!1!rule!3!match!directory = /cherokee_themes
>> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
>> vserver!1!rule!3!handler = file
>>
>> vserver!1!rule!4!match = directory
>> vserver!1!rule!4!match!directory = /cgi-bin
>> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
>> vserver!1!rule!4!handler = cgi
>>
>> vserver!1!rule!5!match = directory
>> vserver!1!rule!5!match!directory = /about
>> vserver!1!rule!5!encoder!gzip = 1
>> vserver!1!rule!5!handler = server_info
>> vserver!1!rule!5!handler!type = just_about
>> _______________________________________________
>> Cherokee mailing list
>> Cherokee [at] lists
>> http://lists.octality.com/listinfo/cherokee
>>
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


me at pigmej

May 8, 2011, 7:29 AM

Post #4 of 15 (980 views)
Permalink
Re: new to cherokee [In reply to]

Well... You need to run it and 'keep it' it's not a daemon ;)


Pozdrawiam
Jędrzej Nowak



2011/5/8 Ryan B <mp3geek [at] gmail>:
> Ah, but I did :)
>
> root [at] server:~# lynx http://localhost:9090
>
> Looking up localhost:9090
> Making HTTP connection to localhost:9090
> Alert!: Unable to connect to remote host.
>
> lynx: Can't access startfile http://localhost:9090/
>
> Nothing is showing in ps, so it's not surprising lynx can't load it
>
>
> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>> If you're new:
>>
>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>> ## then proceed to point your web browser to: http://localhost:9090/
>>
>> You should read that lines in .conf ;)
>>
>> Just run cherokee-admin ;)
>>
>> Greetings,
>> Jędrzej Nowak
>>
>>
>>
>> On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
>>> Installing from a tarball and compiled, but when I start it
>>> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>>>
>>> root [at] server:/etc/init.d# ./cherokee start
>>> Starting cherokee web server: cherokee.
>>> root [at] server:/etc/init.d# ps aux | grep chero
>>> root     13513  0.0  0.2   1876   596 pts/0    S+   18:04   0:00 grep
>>> --color=auto chero
>>> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
>>> ##
>>> ## cherokee.conf -- Cherokee HTTP server configuration file
>>> ##
>>> ## Common use
>>> ##
>>> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
>>> ## convenient configuration interface is available, so the server can
>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>> ## then proceed to point your web browser to: http://localhost:9090/
>>> ##
>>>
>>> # Server
>>> #
>>> server!bind!1!port = 80
>>> server!timeout = 15
>>> server!keepalive = 1
>>> server!keepalive_max_requests = 500
>>> server!server_tokens = full
>>> server!panic_action = /usr/local/bin/cherokee-panic
>>> server!pid_file = /var/run/cherokee.pid
>>>
>>> # Default virtual server
>>> #
>>> vserver!1!nick = default
>>> vserver!1!document_root = /var/www
>>> vserver!1!directory_index = index.html
>>>
>>> vserver!1!logger = combined
>>> vserver!1!logger!access!type = file
>>> vserver!1!logger!access!filename = /var/log/cherokee.access
>>> vserver!1!logger!access!buffsize = 16384
>>>
>>> vserver!1!error_writer!type = file
>>> vserver!1!error_writer!filename = /var/log/cherokee.error
>>>
>>> vserver!1!rule!1!match = default
>>> vserver!1!rule!1!handler = common
>>> vserver!1!rule!1!handler!iocache = 1
>>>
>>> vserver!1!rule!2!match = directory
>>> vserver!1!rule!2!match!directory = /icons
>>> vserver!1!rule!2!handler = file
>>> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>>>
>>> vserver!1!rule!3!match = directory
>>> vserver!1!rule!3!match!directory = /cherokee_themes
>>> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
>>> vserver!1!rule!3!handler = file
>>>
>>> vserver!1!rule!4!match = directory
>>> vserver!1!rule!4!match!directory = /cgi-bin
>>> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
>>> vserver!1!rule!4!handler = cgi
>>>
>>> vserver!1!rule!5!match = directory
>>> vserver!1!rule!5!match!directory = /about
>>> vserver!1!rule!5!encoder!gzip = 1
>>> vserver!1!rule!5!handler = server_info
>>> vserver!1!rule!5!handler!type = just_about
>>> _______________________________________________
>>> Cherokee mailing list
>>> Cherokee [at] lists
>>> http://lists.octality.com/listinfo/cherokee
>>>
>>
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


mp3geek at gmail

May 8, 2011, 7:36 AM

Post #5 of 15 (994 views)
Permalink
Re: new to cherokee [In reply to]

Okay, managed to get the daemon to stay put, and its running..

root 9311 0.0 0.3 11560 960 ? Sl 18:32 0:00
/usr/local/sbin/cherokee
root 9315 0.0 0.6 37032 1796 ? Sl 18:32 0:00
/usr/local/sbin/cherokee-worker

But lynx doesnt see localhost:9090 (or 127.0.0.1:9090)


2011/5/9 Jędrzej Nowak <me [at] pigmej>:
> Well... You need to run it and 'keep it' it's not a daemon ;)
>
>
> Pozdrawiam
> Jędrzej Nowak
>
>
>
> 2011/5/8 Ryan B <mp3geek [at] gmail>:
>> Ah, but I did :)
>>
>> root [at] server:~# lynx http://localhost:9090
>>
>> Looking up localhost:9090
>> Making HTTP connection to localhost:9090
>> Alert!: Unable to connect to remote host.
>>
>> lynx: Can't access startfile http://localhost:9090/
>>
>> Nothing is showing in ps, so it's not surprising lynx can't load it
>>
>>
>> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>>> If you're new:
>>>
>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>
>>> You should read that lines in .conf ;)
>>>
>>> Just run cherokee-admin ;)
>>>
>>> Greetings,
>>> Jędrzej Nowak
>>>
>>>
>>>
>>> On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
>>>> Installing from a tarball and compiled, but when I start it
>>>> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>>>>
>>>> root [at] server:/etc/init.d# ./cherokee start
>>>> Starting cherokee web server: cherokee.
>>>> root [at] server:/etc/init.d# ps aux | grep chero
>>>> root     13513  0.0  0.2   1876   596 pts/0    S+   18:04   0:00 grep
>>>> --color=auto chero
>>>> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
>>>> ##
>>>> ## cherokee.conf -- Cherokee HTTP server configuration file
>>>> ##
>>>> ## Common use
>>>> ##
>>>> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
>>>> ## convenient configuration interface is available, so the server can
>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>> ##
>>>>
>>>> # Server
>>>> #
>>>> server!bind!1!port = 80
>>>> server!timeout = 15
>>>> server!keepalive = 1
>>>> server!keepalive_max_requests = 500
>>>> server!server_tokens = full
>>>> server!panic_action = /usr/local/bin/cherokee-panic
>>>> server!pid_file = /var/run/cherokee.pid
>>>>
>>>> # Default virtual server
>>>> #
>>>> vserver!1!nick = default
>>>> vserver!1!document_root = /var/www
>>>> vserver!1!directory_index = index.html
>>>>
>>>> vserver!1!logger = combined
>>>> vserver!1!logger!access!type = file
>>>> vserver!1!logger!access!filename = /var/log/cherokee.access
>>>> vserver!1!logger!access!buffsize = 16384
>>>>
>>>> vserver!1!error_writer!type = file
>>>> vserver!1!error_writer!filename = /var/log/cherokee.error
>>>>
>>>> vserver!1!rule!1!match = default
>>>> vserver!1!rule!1!handler = common
>>>> vserver!1!rule!1!handler!iocache = 1
>>>>
>>>> vserver!1!rule!2!match = directory
>>>> vserver!1!rule!2!match!directory = /icons
>>>> vserver!1!rule!2!handler = file
>>>> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>>>>
>>>> vserver!1!rule!3!match = directory
>>>> vserver!1!rule!3!match!directory = /cherokee_themes
>>>> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
>>>> vserver!1!rule!3!handler = file
>>>>
>>>> vserver!1!rule!4!match = directory
>>>> vserver!1!rule!4!match!directory = /cgi-bin
>>>> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
>>>> vserver!1!rule!4!handler = cgi
>>>>
>>>> vserver!1!rule!5!match = directory
>>>> vserver!1!rule!5!match!directory = /about
>>>> vserver!1!rule!5!encoder!gzip = 1
>>>> vserver!1!rule!5!handler = server_info
>>>> vserver!1!rule!5!handler!type = just_about
>>>> _______________________________________________
>>>> Cherokee mailing list
>>>> Cherokee [at] lists
>>>> http://lists.octality.com/listinfo/cherokee
>>>>
>>>
>>
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


me at pigmej

May 8, 2011, 7:38 AM

Post #6 of 15 (986 views)
Permalink
Re: new to cherokee [In reply to]

As I said... run cherokee-admin :) not cherokee/cherokee-worker :)
It's in pref/sbin/cherokee-admin

And cherokee admin is not a daemon :)
On 8 May 2011 16:36, "Ryan B" <mp3geek [at] gmail> wrote:
> Okay, managed to get the daemon to stay put, and its running..
>
> root 9311 0.0 0.3 11560 960 ? Sl 18:32 0:00
> /usr/local/sbin/cherokee
> root 9315 0.0 0.6 37032 1796 ? Sl 18:32 0:00
> /usr/local/sbin/cherokee-worker
>
> But lynx doesnt see localhost:9090 (or 127.0.0.1:9090)
>
>
> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>> Well... You need to run it and 'keep it' it's not a daemon ;)
>>
>>
>> Pozdrawiam
>> Jędrzej Nowak
>>
>>
>>
>> 2011/5/8 Ryan B <mp3geek [at] gmail>:
>>> Ah, but I did :)
>>>
>>> root [at] server:~# lynx http://localhost:9090
>>>
>>> Looking up localhost:9090
>>> Making HTTP connection to localhost:9090
>>> Alert!: Unable to connect to remote host.
>>>
>>> lynx: Can't access startfile http://localhost:9090/
>>>
>>> Nothing is showing in ps, so it's not surprising lynx can't load it
>>>
>>>
>>> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>>>> If you're new:
>>>>
>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>>
>>>> You should read that lines in .conf ;)
>>>>
>>>> Just run cherokee-admin ;)
>>>>
>>>> Greetings,
>>>> Jędrzej Nowak
>>>>
>>>>
>>>>
>>>> On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
>>>>> Installing from a tarball and compiled, but when I start it
>>>>> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>>>>>
>>>>> root [at] server:/etc/init.d# ./cherokee start
>>>>> Starting cherokee web server: cherokee.
>>>>> root [at] server:/etc/init.d# ps aux | grep chero
>>>>> root 13513 0.0 0.2 1876 596 pts/0 S+ 18:04 0:00 grep
>>>>> --color=auto chero
>>>>> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
>>>>> ##
>>>>> ## cherokee.conf -- Cherokee HTTP server configuration file
>>>>> ##
>>>>> ## Common use
>>>>> ##
>>>>> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
>>>>> ## convenient configuration interface is available, so the server can
>>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>>> ##
>>>>>
>>>>> # Server
>>>>> #
>>>>> server!bind!1!port = 80
>>>>> server!timeout = 15
>>>>> server!keepalive = 1
>>>>> server!keepalive_max_requests = 500
>>>>> server!server_tokens = full
>>>>> server!panic_action = /usr/local/bin/cherokee-panic
>>>>> server!pid_file = /var/run/cherokee.pid
>>>>>
>>>>> # Default virtual server
>>>>> #
>>>>> vserver!1!nick = default
>>>>> vserver!1!document_root = /var/www
>>>>> vserver!1!directory_index = index.html
>>>>>
>>>>> vserver!1!logger = combined
>>>>> vserver!1!logger!access!type = file
>>>>> vserver!1!logger!access!filename = /var/log/cherokee.access
>>>>> vserver!1!logger!access!buffsize = 16384
>>>>>
>>>>> vserver!1!error_writer!type = file
>>>>> vserver!1!error_writer!filename = /var/log/cherokee.error
>>>>>
>>>>> vserver!1!rule!1!match = default
>>>>> vserver!1!rule!1!handler = common
>>>>> vserver!1!rule!1!handler!iocache = 1
>>>>>
>>>>> vserver!1!rule!2!match = directory
>>>>> vserver!1!rule!2!match!directory = /icons
>>>>> vserver!1!rule!2!handler = file
>>>>> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>>>>>
>>>>> vserver!1!rule!3!match = directory
>>>>> vserver!1!rule!3!match!directory = /cherokee_themes
>>>>> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
>>>>> vserver!1!rule!3!handler = file
>>>>>
>>>>> vserver!1!rule!4!match = directory
>>>>> vserver!1!rule!4!match!directory = /cgi-bin
>>>>> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
>>>>> vserver!1!rule!4!handler = cgi
>>>>>
>>>>> vserver!1!rule!5!match = directory
>>>>> vserver!1!rule!5!match!directory = /about
>>>>> vserver!1!rule!5!encoder!gzip = 1
>>>>> vserver!1!rule!5!handler = server_info
>>>>> vserver!1!rule!5!handler!type = just_about
>>>>> _______________________________________________
>>>>> Cherokee mailing list
>>>>> Cherokee [at] lists
>>>>> http://lists.octality.com/listinfo/cherokee
>>>>>
>>>>
>>>
>>


mp3geek at gmail

May 8, 2011, 7:54 AM

Post #7 of 15 (986 views)
Permalink
Re: new to cherokee [In reply to]

Okay, got it.. is it possible to run admin on a real-world ip rather
than localhost?

2011/5/9 Jędrzej Nowak <me [at] pigmej>:
> As I said... run cherokee-admin :) not cherokee/cherokee-worker :)
> It's in pref/sbin/cherokee-admin
>
> And cherokee admin is not a daemon :)
>
> On 8 May 2011 16:36, "Ryan B" <mp3geek [at] gmail> wrote:
>> Okay, managed to get the daemon to stay put, and its running..
>>
>> root 9311 0.0 0.3 11560 960 ? Sl 18:32 0:00
>> /usr/local/sbin/cherokee
>> root 9315 0.0 0.6 37032 1796 ? Sl 18:32 0:00
>> /usr/local/sbin/cherokee-worker
>>
>> But lynx doesnt see localhost:9090 (or 127.0.0.1:9090)
>>
>>
>> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>>> Well... You need to run it and 'keep it' it's not a daemon ;)
>>>
>>>
>>> Pozdrawiam
>>> Jędrzej Nowak
>>>
>>>
>>>
>>> 2011/5/8 Ryan B <mp3geek [at] gmail>:
>>>> Ah, but I did :)
>>>>
>>>> root [at] server:~# lynx http://localhost:9090
>>>>
>>>> Looking up localhost:9090
>>>> Making HTTP connection to localhost:9090
>>>> Alert!: Unable to connect to remote host.
>>>>
>>>> lynx: Can't access startfile http://localhost:9090/
>>>>
>>>> Nothing is showing in ps, so it's not surprising lynx can't load it
>>>>
>>>>
>>>> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>>>>> If you're new:
>>>>>
>>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>>>
>>>>> You should read that lines in .conf ;)
>>>>>
>>>>> Just run cherokee-admin ;)
>>>>>
>>>>> Greetings,
>>>>> Jędrzej Nowak
>>>>>
>>>>>
>>>>>
>>>>> On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
>>>>>> Installing from a tarball and compiled, but when I start it
>>>>>> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>>>>>>
>>>>>> root [at] server:/etc/init.d# ./cherokee start
>>>>>> Starting cherokee web server: cherokee.
>>>>>> root [at] server:/etc/init.d# ps aux | grep chero
>>>>>> root     13513  0.0  0.2   1876   596 pts/0    S+   18:04   0:00 grep
>>>>>> --color=auto chero
>>>>>> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
>>>>>> ##
>>>>>> ## cherokee.conf -- Cherokee HTTP server configuration file
>>>>>> ##
>>>>>> ## Common use
>>>>>> ##
>>>>>> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
>>>>>> ## convenient configuration interface is available, so the server can
>>>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>>>> ##
>>>>>>
>>>>>> # Server
>>>>>> #
>>>>>> server!bind!1!port = 80
>>>>>> server!timeout = 15
>>>>>> server!keepalive = 1
>>>>>> server!keepalive_max_requests = 500
>>>>>> server!server_tokens = full
>>>>>> server!panic_action = /usr/local/bin/cherokee-panic
>>>>>> server!pid_file = /var/run/cherokee.pid
>>>>>>
>>>>>> # Default virtual server
>>>>>> #
>>>>>> vserver!1!nick = default
>>>>>> vserver!1!document_root = /var/www
>>>>>> vserver!1!directory_index = index.html
>>>>>>
>>>>>> vserver!1!logger = combined
>>>>>> vserver!1!logger!access!type = file
>>>>>> vserver!1!logger!access!filename = /var/log/cherokee.access
>>>>>> vserver!1!logger!access!buffsize = 16384
>>>>>>
>>>>>> vserver!1!error_writer!type = file
>>>>>> vserver!1!error_writer!filename = /var/log/cherokee.error
>>>>>>
>>>>>> vserver!1!rule!1!match = default
>>>>>> vserver!1!rule!1!handler = common
>>>>>> vserver!1!rule!1!handler!iocache = 1
>>>>>>
>>>>>> vserver!1!rule!2!match = directory
>>>>>> vserver!1!rule!2!match!directory = /icons
>>>>>> vserver!1!rule!2!handler = file
>>>>>> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>>>>>>
>>>>>> vserver!1!rule!3!match = directory
>>>>>> vserver!1!rule!3!match!directory = /cherokee_themes
>>>>>> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
>>>>>> vserver!1!rule!3!handler = file
>>>>>>
>>>>>> vserver!1!rule!4!match = directory
>>>>>> vserver!1!rule!4!match!directory = /cgi-bin
>>>>>> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
>>>>>> vserver!1!rule!4!handler = cgi
>>>>>>
>>>>>> vserver!1!rule!5!match = directory
>>>>>> vserver!1!rule!5!match!directory = /about
>>>>>> vserver!1!rule!5!encoder!gzip = 1
>>>>>> vserver!1!rule!5!handler = server_info
>>>>>> vserver!1!rule!5!handler!type = just_about
>>>>>> _______________________________________________
>>>>>> Cherokee mailing list
>>>>>> Cherokee [at] lists
>>>>>> http://lists.octality.com/listinfo/cherokee
>>>>>>
>>>>>
>>>>
>>>
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


me at pigmej

May 8, 2011, 7:55 AM

Post #8 of 15 (985 views)
Permalink
Re: new to cherokee [In reply to]

cherokee-admin -b ;-) + read the docs ;)
Pozdrawiam
Jędrzej Nowak



2011/5/8 Ryan B <mp3geek [at] gmail>:
> Okay, got it.. is it possible to run admin on a real-world ip rather
> than localhost?
>
> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>> As I said... run cherokee-admin :) not cherokee/cherokee-worker :)
>> It's in pref/sbin/cherokee-admin
>>
>> And cherokee admin is not a daemon :)
>>
>> On 8 May 2011 16:36, "Ryan B" <mp3geek [at] gmail> wrote:
>>> Okay, managed to get the daemon to stay put, and its running..
>>>
>>> root 9311 0.0 0.3 11560 960 ? Sl 18:32 0:00
>>> /usr/local/sbin/cherokee
>>> root 9315 0.0 0.6 37032 1796 ? Sl 18:32 0:00
>>> /usr/local/sbin/cherokee-worker
>>>
>>> But lynx doesnt see localhost:9090 (or 127.0.0.1:9090)
>>>
>>>
>>> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>>>> Well... You need to run it and 'keep it' it's not a daemon ;)
>>>>
>>>>
>>>> Pozdrawiam
>>>> Jędrzej Nowak
>>>>
>>>>
>>>>
>>>> 2011/5/8 Ryan B <mp3geek [at] gmail>:
>>>>> Ah, but I did :)
>>>>>
>>>>> root [at] server:~# lynx http://localhost:9090
>>>>>
>>>>> Looking up localhost:9090
>>>>> Making HTTP connection to localhost:9090
>>>>> Alert!: Unable to connect to remote host.
>>>>>
>>>>> lynx: Can't access startfile http://localhost:9090/
>>>>>
>>>>> Nothing is showing in ps, so it's not surprising lynx can't load it
>>>>>
>>>>>
>>>>> 2011/5/9 Jędrzej Nowak <me [at] pigmej>:
>>>>>> If you're new:
>>>>>>
>>>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>>>>
>>>>>> You should read that lines in .conf ;)
>>>>>>
>>>>>> Just run cherokee-admin ;)
>>>>>>
>>>>>> Greetings,
>>>>>> Jędrzej Nowak
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, May 8, 2011 at 4:07 PM, Ryan B <mp3geek [at] gmail> wrote:
>>>>>>> Installing from a tarball and compiled, but when I start it
>>>>>>> "/etc/init.d/cherokee start", no cherokee log files in /var/log/
>>>>>>>
>>>>>>> root [at] server:/etc/init.d# ./cherokee start
>>>>>>> Starting cherokee web server: cherokee.
>>>>>>> root [at] server:/etc/init.d# ps aux | grep chero
>>>>>>> root     13513  0.0  0.2   1876   596 pts/0    S+   18:04   0:00 grep
>>>>>>> --color=auto chero
>>>>>>> root [at] server:/etc/init.d# cat /etc/cherokee/cherokee.conf
>>>>>>> ##
>>>>>>> ## cherokee.conf -- Cherokee HTTP server configuration file
>>>>>>> ##
>>>>>>> ## Common use
>>>>>>> ##
>>>>>>> ## NOTE: This file is NOT meant to be edited by hand. Instead, a
>>>>>>> ## convenient configuration interface is available, so the server can
>>>>>>> ## be tweaked in a easy and safe way. Run cherokee-admin as root, and
>>>>>>> ## then proceed to point your web browser to: http://localhost:9090/
>>>>>>> ##
>>>>>>>
>>>>>>> # Server
>>>>>>> #
>>>>>>> server!bind!1!port = 80
>>>>>>> server!timeout = 15
>>>>>>> server!keepalive = 1
>>>>>>> server!keepalive_max_requests = 500
>>>>>>> server!server_tokens = full
>>>>>>> server!panic_action = /usr/local/bin/cherokee-panic
>>>>>>> server!pid_file = /var/run/cherokee.pid
>>>>>>>
>>>>>>> # Default virtual server
>>>>>>> #
>>>>>>> vserver!1!nick = default
>>>>>>> vserver!1!document_root = /var/www
>>>>>>> vserver!1!directory_index = index.html
>>>>>>>
>>>>>>> vserver!1!logger = combined
>>>>>>> vserver!1!logger!access!type = file
>>>>>>> vserver!1!logger!access!filename = /var/log/cherokee.access
>>>>>>> vserver!1!logger!access!buffsize = 16384
>>>>>>>
>>>>>>> vserver!1!error_writer!type = file
>>>>>>> vserver!1!error_writer!filename = /var/log/cherokee.error
>>>>>>>
>>>>>>> vserver!1!rule!1!match = default
>>>>>>> vserver!1!rule!1!handler = common
>>>>>>> vserver!1!rule!1!handler!iocache = 1
>>>>>>>
>>>>>>> vserver!1!rule!2!match = directory
>>>>>>> vserver!1!rule!2!match!directory = /icons
>>>>>>> vserver!1!rule!2!handler = file
>>>>>>> vserver!1!rule!2!document_root = /usr/local/share/cherokee/icons
>>>>>>>
>>>>>>> vserver!1!rule!3!match = directory
>>>>>>> vserver!1!rule!3!match!directory = /cherokee_themes
>>>>>>> vserver!1!rule!3!document_root = /usr/local/share/cherokee/themes
>>>>>>> vserver!1!rule!3!handler = file
>>>>>>>
>>>>>>> vserver!1!rule!4!match = directory
>>>>>>> vserver!1!rule!4!match!directory = /cgi-bin
>>>>>>> vserver!1!rule!4!document_root = NONE/lib/cgi-bin
>>>>>>> vserver!1!rule!4!handler = cgi
>>>>>>>
>>>>>>> vserver!1!rule!5!match = directory
>>>>>>> vserver!1!rule!5!match!directory = /about
>>>>>>> vserver!1!rule!5!encoder!gzip = 1
>>>>>>> vserver!1!rule!5!handler = server_info
>>>>>>> vserver!1!rule!5!handler!type = just_about
>>>>>>> _______________________________________________
>>>>>>> Cherokee mailing list
>>>>>>> Cherokee [at] lists
>>>>>>> http://lists.octality.com/listinfo/cherokee
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


mp3geek at gmail

May 8, 2011, 8:56 AM

Post #9 of 15 (974 views)
Permalink
Re: new to cherokee [In reply to]

A few questions about functionality of cherokee,

I see theres an global keepalive in the admin website, is it possible
to have a certain dir/ with its own keepalive disabled?


I have 2 files,
file.txt
file.txt.gz

In nginx I can will detect that someone is requesting "file.txt" so
instead sending a newly compressed gzip copy, it'll take the existing
gzip file.
http://wiki.nginx.org/HttpGzipStaticModule

Is this possible in cherokee?
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


alvaro at octality

May 8, 2011, 9:54 AM

Post #10 of 15 (972 views)
Permalink
Re: new to cherokee [In reply to]

Hello Ryan,

On Sun, May 8, 2011 at 5:56 PM, Ryan B <mp3geek [at] gmail> wrote:

> A few questions about functionality of cherokee,
>
> I see theres an global keepalive in the admin website, is it possible
> to have a certain dir/ with its own keepalive disabled?
>

No, it is not. Why would do that?


> I have 2 files,
> file.txt
> file.txt.gz
>
> In nginx I can will detect that someone is requesting "file.txt" so
> instead sending a newly compressed gzip copy, it'll take the existing
> gzip file.
> http://wiki.nginx.org/HttpGzipStaticModule
>
> Is this possible in cherokee?
>

It's about to be possible with the upcoming version of the Cherokee. A new
subsystem called "Front-Line
Cache<http://www.alobbs.com/1392/Front_Line_Cache.html>"
has been integrated in the server core. Among many other things, Front-Line
cache allows to cache encoded version of static files.

--
Greetings, alo
http://www.octality.com/


mp3geek at gmail

May 8, 2011, 4:53 PM

Post #11 of 15 (971 views)
Permalink
Re: new to cherokee [In reply to]

This is what I'm basically after,

Theres 2 purposes to the website, one is the website is front end
(keep alive is fine), but the other purpose is to serve files which I
require a keep alive to be 0.

www.domain.com -> /var/www (keepalive on)
files.domain.com -> /var/www/files (keepalive off)

>> In nginx I can will detect that someone is requesting "file.txt" so
>> instead sending a newly compressed gzip copy, it'll take the existing
>> gzip file.
>> http://wiki.nginx.org/HttpGzipStaticModule
>>
>> Is this possible in cherokee?
>
> It's about to be possible with the upcoming version of the Cherokee. A new
> subsystem called "Front-Line Cache" has been integrated in the server core.
> Among many other things, Front-Line cache allows to cache encoded version of
> static files.

Awesome! I'm using the svn snapshot, how do I enable/use it?
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


mp3geek at gmail

May 8, 2011, 6:55 PM

Post #12 of 15 (969 views)
Permalink
Re: new to cherokee [In reply to]

>> It's about to be possible with the upcoming version of the Cherokee. A new
>> subsystem called "Front-Line Cache" has been integrated in the server core.
>> Among many other things, Front-Line cache allows to cache encoded version of
>> static files.
>
> Awesome! I'm using the svn snapshot, how do I enable/use it?
>

Followed through this post
http://lists.octality.com/pipermail/cherokee-dev/2011-May/006861.html

It still seems to be compressing the the file, rather than using the
existing .gz

http://imgur.com/a/CMigw#Aab8N

Not sure what I've mis-configured,

With the final pic, http://i.imgur.com/W4DV9.jpg (showing a difference
between whats received vs on the server)
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee


alvaro at octality

May 12, 2011, 6:05 AM

Post #13 of 15 (937 views)
Permalink
Re: new to cherokee [In reply to]

On Mon, May 9, 2011 at 1:53 AM, Ryan B <mp3geek [at] gmail> wrote:

> > It's about to be possible with the upcoming version of the Cherokee. A
> new
> > subsystem called "Front-Line Cache" has been integrated in the server
> core.
> > Among many other things, Front-Line cache allows to cache encoded version
> of
> > static files.
>
> Awesome! I'm using the svn snapshot, how do I enable/use it?


There is a wizard for it.

Check the "Cache" tab of the rules if you prefer to configure it by hand.

--
Greetings, alo
http://www.octality.com/


alvaro at octality

May 12, 2011, 6:13 AM

Post #14 of 15 (943 views)
Permalink
Re: new to cherokee [In reply to]

Hello Ryan,

On Mon, May 9, 2011 at 3:55 AM, Ryan B <mp3geek [at] gmail> wrote:

> >> It's about to be possible with the upcoming version of the Cherokee. A
> new
> >> subsystem called "Front-Line Cache" has been integrated in the server
> core.
> >> Among many other things, Front-Line cache allows to cache encoded
> version of
> >> static files.
> >
> > Awesome! I'm using the svn snapshot, how do I enable/use it?
> >
>
> Followed through this post
> http://lists.octality.com/pipermail/cherokee-dev/2011-May/006861.html
>
> It still seems to be compressing the the file, rather than using the
> existing .gz
>

Yes. Actually, Front-Line cache purpose is to cache responses, not to map
content to local files that you have previously compresses by hand. (...
which looks to me like a 90s hackish workaround for the lack of a mechanism
like Front-Line Cache).

Front-Line Cache will cache compressed (and not compressed) responses
locally, so Cherokee doesn't have to re-compress the same response twice
while the cache object is 'fresh'.

There is no need to do something by hand (compress files) when the server
can do it for you seamlessly.

--
Greetings, alo
http://www.octality.com/


alvaro at octality

Aug 26, 2011, 11:32 AM

Post #15 of 15 (782 views)
Permalink
Re: New to Cherokee [In reply to]

Hello Todd,

On Fri, Aug 26, 2011 at 7:42 PM, Todd Rafferty <webrat [at] gmail> wrote:

>
> I'm new to the Cherokee project and after having played around with it for
> a week or so, I'm pretty impressed with it. I noticed that Cherokee has
> support for Adobe ColdFusion out of the box. Was wondering what it would
> take to get something similar for Railo (open source CFML Engine) -
> http://getrailo.org/. It took all but 2 minutes to get Railo/Tomcat up and
> running with Cherokee provided you know which panels and buttons to push.
>
> Is there someone I can talk to or can someone point me in the right
> direction?
>

We are currently working on a revised version of the Wizard mechanism. So
far there are only a couple of wizards ported to the new system, but it'd be
great to get new ones wizards while we port the existing ones.

If you want to check it out, the code is available at svn://
svn.cherokee-project.com/wizards2

Cheers!

--
Greetings, alo
http://www.octality.com/

Cherokee users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.