2010/6/24 Alvaro Lopez Ortega <[email protected]>

> On 24/06/2010, at 00:59, C. Mundi wrote:
> > On 6/23/10, Alvaro Lopez Ortega <[email protected]> wrote:
> >> On 23/06/2010, at 20:14, Álvaro Pinel Bueno wrote:
> >>
> >>> Hi, I'm learning cherokee and django, I'm triying to follow the steps
> in
> >>> http://www.cherokee-project.com/doc/cookbook_django.html but it
> doesn't
> >>> work.
> >>>
> >>> I have created and django example project in /var/www/example but my
> >>> doubts are:
> >>>
> >>> Differents between Document Root and Project Directory.
> >>
> >> As the documentation page that you refereed reads:
> >>
> >> ===
> >> Project Directory applies to the path where your Django application is
> >> located, while Document Root applies to the directory that contains
> >> non-Django related files, such as any static content.
> >> ===
> >
> > I suffered the same confusion at first.  The context of phrases like
> > "path" and "directory" is important.
>
> Proposals on how to disambiguate those terms are more than welcome.
>
>

I think of them as 'filesystem root' and 'document root' or 'server root'
but anyone could claim that those are just as ambiguous.  Of course things
get more complicated if there are additional middleware (e.g. WSGI),
frameworks (e.g. Django, Drupal) and applications (e.g. django apps and
drupal modules).  Each "layer" introduces at least one kind of base
directory.  One could say that the meaning of the base directory is always
clear from context.  Well, that's true if the context is always clear!
Unfortunately, that's not the case in my experience, because most people
setting out to create a website are trying to figure everything out at once
as quickly as possible.  I'm not saying that's the "right" way.  I'm just
saying that's what actually happens.   And although it is possible in
practice, specifying the context explicitly in every case quickly becomes
awkward, even among English speakers like me who tend to be very forgiving
about crushing adjectives and nouns together in ungrammatical ways.  :)
Perhaps the most useful thing would be to leave the nomenclature alone -- it
is after all consistent with other webservers -- and simply elaborate on the
already very helpful "hints" in the cherokee-admin interface.  I will take a
look the next time I'm in there and see of I can offer some suggestions.

Thanks!
cm
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to