headers
Shane Volpe | 1 Apr 2008 12:25
Picon

Disabling Directory indexing is on in cherokee

How do you disable directory indexing on Cherokee for a given site?
Regards,
Shane
Permalink | Reply | 2 comments |
headers
Shane Volpe | 1 Apr 2008 12:33
Picon

Re: Disabling Directory indexing is on in cherokee

I forgot to mention that I'm using Cherokee 0.6 and its an embedded
system so using cherokee-admin is not an option.

On Tue, Apr 1, 2008 at 6:25 AM, Shane Volpe <shanevolpe <at> gmail.com> wrote:
> How do you disable directory indexing on Cherokee for a given site?
>  Regards,
>  Shane
>

--

-- 
Registered Linux User: #293401
Permalink | Reply | 1 comment |
headers
Taher Shihadeh | 1 Apr 2008 13:39

Re: Disabling Directory indexing is on in cherokee

Hi Shane.
The idea behind cherokee-admin is that it should always be an option to avoid the configuration hassle. For
minimal environments cherokee-admin should be used on another machine and then copy the resulting
configuration file to the embedded device.

You'll be using another computer to develop whatever application you are working on, so this shouldn't be a problem.

On 01 Apr 2008, Shane Volpe wrote:
> I forgot to mention that I'm using Cherokee 0.6 and its an embedded
> system so using cherokee-admin is not an option.
> 
> On Tue, Apr 1, 2008 at 6:25 AM, Shane Volpe <shanevolpe <at> gmail.com> wrote:
> > How do you disable directory indexing on Cherokee for a given site?
> >  Regards,
> >  Shane

--

-- 
taher <at> unixwars.com
http://unixwars.com
Permalink | Reply | 0 comments |
headers
Shane Volpe | 1 Apr 2008 14:27
Picon

Re: Fwd: Disabling Directory indexing is on in cherokee

is there any place I can get documentation on the 0.6 config format,
for instance how would I know how to generate the line
"vserver!leemelo.com!directory!/!priority" unless I used
cherokee-admin.  I understand that I'm developing my embedded system
on a host computer but all my debugging and web page design occurs on
my target device.  It *WILL* be quite a hassle to have to use
cherokee-admin on my host, copy my config files over to the target and
then debug it on the target.
Regards,
Shane

On Tue, Apr 1, 2008 at 8:23 AM, Miguel Angel Ajo Pelayo
<miguelangel <at> ajo.es> wrote:
> Hi Nikolai,
>
>
>     Right now, cherokee-admin reads, and generates the file cherokee.conf at
> /etc/cherokee/
>
> It's a plain text config file with a simple formatting designed to be fast
> and simple to parse.
>
> I paste here an snippet of my config for you to see how does it look like:
> [---------------------------------------------------------------------]
> vserver!leemelo.com!directory!/icons!handler!theme = firefox3
>  vserver!leemelo.com!directory!/icons!handler!user = 0
> vserver!leemelo.com!directory!/icons!handler!date = 1
> vserver!leemelo.com!directory!/icons!handler!size = 1
> vserver!leemelo.com!directory!/icons!document_root =
> /usr/share/cherokee/icons/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Taher Shihadeh | 1 Apr 2008 14:43

Re: Disabling Directory indexing is on in cherokee

On 01 Apr 2008, Nikolai Kondrashov escribiówrote:
>  > avoid the configuration hassle. For minimal environments cherokee-admin
>  > should be used on another machine and then copy the resulting
>  > configuration file to the embedded device.
> I agree, but there should also be an option to have as complex configuration
> as needed.

Agreed. When I said 'minimal environments' y meant 'embedded environments', not 'minimal configuration'.
cherokee-admin is new since release 0.6, so it figures any shortcomings will be solved/enhanced.
For example a few days back, thanks to a question sent to this list, Alvaro noticed that the number of threads
wasn't managed through cherokee-admin. He sumbitted changes to cherokee-admin the same day. I don't
remember right now if it's allready in 0.6.1, but I'm quite sure I've seen the modification in SVN.

We do monitor whatever is said here. Don't hesitate to ask for improvements.

> We will need the ability to configure other Web-server parameters, very
> probably, which could easily be accomplished through a configuration file
> generation both at run time and at build time. And without proper
> configuration file documentation I will need to dig into source code.

Well... there is always the info provided at http://www.cherokee-project.com/doc/internal_configuration.html
Documentation, however, could and should always be improved. Work in progress there ;)

> Of course providing a possibility for hard-coded configuration would satisfy
> our needs, but, having possibility to generate the configuration file is
> much nicer.

I don't think I quite understood you here, sorry. 
If by generating the config file you mean having nicer documentation on the internal format, what is this
hard-coded configuration you talk about: using cherokee-admin as is, improving some missing features...?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nikolai Kondrashov | 1 Apr 2008 15:44
Picon
Favicon

Re: Disabling Directory indexing is on in cherokee

Taher Shihadeh wrote:
 > Agreed. When I said 'minimal environments' y meant 'embedded environments', not 'minimal configuration'.
Yes, but using cherokee-admin somewhat implies 'minimal configuration' when
compared to the set of every possible configuration.

 > We do monitor whatever is said here. Don't hesitate to ask for improvements.
Thanks, I will :)! And I hope these improvements, if implemented, will be
useful for someone else :)

 > Well... there is always the info provided at
 > http://www.cherokee-project.com/doc/internal_configuration.html
Thanks, haven't seen that page yet :)

 > what is this hard-coded configuration you talk about: using cherokee-admin
 > as is, improving some missing features...?
I meant the way u-Cherokee is configured, i.e. by modifying
read_config_embedded.c

Sincerely,
Nick
Permalink | Reply | 0 comments |
headers
Gunnar Wolf | 1 Apr 2008 18:03
Gravatar

Re: Request for help: Fixing 05to06.py?

Alvaro Lopez Ortega dijo [Fri, Mar 28, 2008 at 12:38:16PM +0100]:
> Let's try to be pragmatic here. Cherokee-admin does not support  
> splitted files, and moreover it will not support it in the near future.
> 
> In fact, I am not even sure whether it is desirable thing to implement  
> in Cherokee. It looks much more like the "less stinky" solution for  
> dealing with text plain configuration files.
> 
> Cherokee 0.5 used splitted configuration files because it was the best  
> solution at that point, but things have changed a lot since then. In  
> fact, I have put a whole lot of work to get rid of it.
> 
> In my opinion, it would make much more sense to allow the web based  
> applications to 'enhance' cherokee-admin by adding some sort of  
> definitions file. In fact, *the server configuration* is a single  
> thing that ought to be treated as such.
> 
> Let's try not to copy the workarounds that other projects were forced  
> to implement. We should try to thing ahead that!

Umh... I perfectly understand Cherokee is not by far among the most
popular webservers - But looking at the standard practices both inside
distributions (i.e. in Debian, that's what I can speak about) and for
Web application authors, it's customary to ship your code with a very
simple configuration snippet, following a easy to understand (or at
least, widely understood) configuration syntax.

Such developers should not be expected to write a configuration module
for an obscure Webserver. They won't do it. That's more likely to
isolate Cherokee even more.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Shane Volpe | 1 Apr 2008 19:29
Picon

Re: Disabling Directory indexing is on in cherokee

It has been a very good conversation but back to my original question:
 I want to disable the automatic directory (file) indexing (listing ?)
so the contents of a directory on my system will not get served up on
a web page.  What would be the 0.6 Cherokee syntax to do this in the
config file?
Regards,
Shane

On Tue, Apr 1, 2008 at 11:54 AM, Gunnar Wolf <gwolf <at> gwolf.org> wrote:
> Taher Shihadeh dijo [Tue, Apr 01, 2008 at 01:39:16PM +0200]:
>
> > Hi Shane.
>  >
>  > The idea behind cherokee-admin is that it should always be an option
>  > to avoid the configuration hassle. For minimal environments
>  > cherokee-admin should be used on another machine and then copy the
>  > resulting configuration file to the embedded device.
>  >
>  > You'll be using another computer to develop whatever application you
>  > are working on, so this shouldn't be a problem.
>
>  Frankly speaking, this seems like a very flawed argument.
>
>  Cherokee-admin is a nice tool. But denying the user the ability to
>  modify the configuration file on his own, using the same tools he has
>  always used for any other Unixy daemon... Is a big demotivator. The
>  need to use cherokee-admin makes the whole program (even if it is
>  not - even without even looking at it!) seem fragile and
>  Windows-like.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Taher Shihadeh | 1 Apr 2008 20:20

Re: Disabling Directory indexing is on in cherokee

Hi Shane!

On Tuesday 01 April 2008 19:29:07, Shane Volpe wrote:
> It has been a very good conversation but back to my original question:
>  I want to disable the automatic directory (file) indexing (listing ?)
> so the contents of a directory on my system will not get served up on
> a web page.  What would be the 0.6 Cherokee syntax to do this in the
> config file?

I've reviewed what I sent you in the last message and I can't believe I actually forgot to answer the original
question X-)

I think you need the handler named 'file'.
For example this prevents the directory indexing of the '/images' directory on my default Virtual Server.

vserver!default!directory!/images!priority = 100099
vserver!default!directory!/images!only_secure = 0
vserver!default!directory!/images!handler = file
vserver!default!directory!/images!handler!iocache = 1

That is what cherokee-admin spits directly. I've just made the test and the Handler I selected for this (in
Virtual Servers-> default ->Behaviour tab) is called 'Static content'

Regards,
	Taher
--

-- 
taher <at> unixwars.com
http://unixwars.com
Permalink | Reply | 0 comments |
headers
Alvaro Lopez Ortega | 2 Apr 2008 16:48
Picon

Re: Request for help: Fixing 05to06.py?

On 2 Apr 2008, at 16:11, Gunnar Wolf wrote:
>>
>> Would a command line utility for merging, removing and modifying
>> configuration files help here?
>
> I think that's the easiest way out. I was thinking whether to modify
> 05to06.py to do this (although my Python is sucky) or to integrate it
> from the Debian Cherokee preinst script - I think it is in Cherokee's
> best interest to do it from 05to06.

Ok, I see what you mean. That's something that we can do if you are so  
use that Linux distros do need it.

Besides, the idea of using wizards for installing third party web  
software from cherokee-admin is something we will implement for  
improving the medium term user experience.

--
Greetings, alo.
Permalink | Reply | 0 comments |

Gmane