Mailing List Archive

May 8, 2011, 7:12 AM

Post #2 of 15 (5042 views)

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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
> Starting cherokee web server: cherokee.
> root@server1:/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@server1:/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@lists.octality.com
> http://lists.octality.com/listinfo/cherokee
>
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 7:25 AM

Post #3 of 15 (5030 views)

Ah, but I did :)

root@server1:~# 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@pigmej.eu>:
> 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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
>> Starting cherokee web server: cherokee.
>> root@server1:/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@server1:/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@lists.octality.com
>> http://lists.octality.com/listinfo/cherokee
>>
>
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 7:29 AM

Post #4 of 15 (5019 views)

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

Pozdrawiam
JÄ™drzej Nowak

2011/5/8 Ryan B <mp3geek@gmail.com>:
> Ah, but I did :)
>
> root@server1:~# 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@pigmej.eu>:
>> 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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
>>> Starting cherokee web server: cherokee.
>>> root@server1:/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@server1:/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@lists.octality.com
>>> http://lists.octality.com/listinfo/cherokee
>>>
>>
>
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 7:36 AM

Post #5 of 15 (5056 views)

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@pigmej.eu>:
> Well... You need to run it and 'keep it' it's not a daemon ;)
>
>
> Pozdrawiam
> JÄ™drzej Nowak
>
>
>
> 2011/5/8 Ryan B <mp3geek@gmail.com>:
>> Ah, but I did :)
>>
>> root@server1:~# 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@pigmej.eu>:
>>> 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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
>>>> Starting cherokee web server: cherokee.
>>>> root@server1:/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@server1:/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@lists.octality.com
>>>> http://lists.octality.com/listinfo/cherokee
>>>>
>>>
>>
>
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 7:38 AM

Post #6 of 15 (5030 views)

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@gmail.com> 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@pigmej.eu>:
>> Well... You need to run it and 'keep it' it's not a daemon ;)
>>
>>
>> Pozdrawiam
>> JÄ™drzej Nowak
>>
>>
>>
>> 2011/5/8 Ryan B <mp3geek@gmail.com>:
>>> Ah, but I did :)
>>>
>>> root@server1:~# 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@pigmej.eu>:
>>>> 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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
>>>>> Starting cherokee web server: cherokee.
>>>>> root@server1:/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@server1:/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@lists.octality.com
>>>>> http://lists.octality.com/listinfo/cherokee
>>>>>
>>>>
>>>
>>

Re: new to cherokee [ In reply to ]

May 8, 2011, 7:54 AM

Post #7 of 15 (5039 views)

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

2011/5/9 JÄ™drzej Nowak <me@pigmej.eu>:
> 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@gmail.com> 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@pigmej.eu>:
>>> Well... You need to run it and 'keep it' it's not a daemon ;)
>>>
>>>
>>> Pozdrawiam
>>> JÄ™drzej Nowak
>>>
>>>
>>>
>>> 2011/5/8 Ryan B <mp3geek@gmail.com>:
>>>> Ah, but I did :)
>>>>
>>>> root@server1:~# 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@pigmej.eu>:
>>>>> 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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
>>>>>> Starting cherokee web server: cherokee.
>>>>>> root@server1:/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@server1:/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@lists.octality.com
>>>>>> http://lists.octality.com/listinfo/cherokee
>>>>>>
>>>>>
>>>>
>>>
>
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 7:55 AM

Post #8 of 15 (5031 views)

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

2011/5/8 Ryan B <mp3geek@gmail.com>:
> Okay, got it.. is it possible to run admin on a real-world ip rather
> than localhost?
>
> 2011/5/9 JÄ™drzej Nowak <me@pigmej.eu>:
>> 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@gmail.com> 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@pigmej.eu>:
>>>> Well... You need to run it and 'keep it' it's not a daemon ;)
>>>>
>>>>
>>>> Pozdrawiam
>>>> JÄ™drzej Nowak
>>>>
>>>>
>>>>
>>>> 2011/5/8 Ryan B <mp3geek@gmail.com>:
>>>>> Ah, but I did :)
>>>>>
>>>>> root@server1:~# 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@pigmej.eu>:
>>>>>> 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@gmail.com> 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@server1:/etc/init.d# ./cherokee start
>>>>>>> Starting cherokee web server: cherokee.
>>>>>>> root@server1:/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@server1:/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@lists.octality.com
>>>>>>> http://lists.octality.com/listinfo/cherokee
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 8:56 AM

Post #9 of 15 (5036 views)

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@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 9:54 AM

Post #10 of 15 (5030 views)

Hello Ryan,

On Sun, May 8, 2011 at 5:56 PM, Ryan B <mp3geek@gmail.com> 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/

Re: new to cherokee [ In reply to ]

May 8, 2011, 4:53 PM

Post #11 of 15 (5025 views)

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@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 8, 2011, 6:55 PM

Post #12 of 15 (5027 views)

>> 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@lists.octality.com
http://lists.octality.com/listinfo/cherokee

Re: new to cherokee [ In reply to ]

May 12, 2011, 6:05 AM

Post #13 of 15 (4994 views)

On Mon, May 9, 2011 at 1:53 AM, Ryan B <mp3geek@gmail.com> 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/

Re: new to cherokee [ In reply to ]

May 12, 2011, 6:13 AM

Post #14 of 15 (4992 views)

Hello Ryan,

On Mon, May 9, 2011 at 3:55 AM, Ryan B <mp3geek@gmail.com> 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/

Re: New to Cherokee [ In reply to ]

Aug 26, 2011, 11:32 AM

Post #15 of 15 (4840 views)