Hi,
I have recently discovered Cherokee and have been spending the last
few days exploring it in the hopes of deploying it on a web server. I am
running Debian squeeze and am currently using the in-tree package
(Cherokee v1.0.8).
I currently have the following web content structure on my existing
web server (running Apache):
For the purposes of this e-mail I'll use the hostname of: www.site.com
/var/www/. - dokuwiki providing main site for www.site.com
/var/www/docs/. - completely separate dokuwiki providing other
information, reachable from
http://www.site.com/docs/
/var/www/thing/. - independent vendor-supplied web content,
reachable from
http://www.site.com/thing/
Working off of information on the main cherokee project site, mailing
list archives, google searches, and
http://noirbizarre.info/2010/12/04/dokuwiki-et-cherokee/, I have been
as-yet-unsuccessful in getting dokuwiki fully-cooperating (it quickly
404's on me if I try to do access anything other than the stock
doku.php), but I haven't yet ruled out errors on my part from not fully
comprehending the mentioned tutorial (French is not my primary
language... fourth at best following C and Bash). So I'm still combing
through that tutorial.
But I am experiencing other problems that I suspect preempt my
dokuwiki issues, and that is the following:
Because I only have one web host, hosting multiple pieces of separate
web content reachable at one name, my current understanding of Cherokee
lingo has me attempting to run a separate virtual server for each item.
For example, I have the following virtual servers:
docs docroot: /var/www/docs
thing docroot: /var/www/thing
default docroot: /var/www
I've set up logging on each virtual server to unique files:
/var/log/cherokee/{default,docs,thing}.{access,error}
I believe I have a problem because everytime I try to hit /docs/, its
logs remain empty and information (be it 404 messages or accesses to the
docs/ dokuwiki data) accumulates in default.access... same when I try to
hit anything in thing/
In the process I thought I might be abusing the notion of default, so
I've also tried scenarios as follows:
main docroot: /var/www/main (moved all pertinent data from
/var/www here)
docs docroot: /var/www/docs
thing docroot: /var/www/thing
default docroot: /var/www (essentially a content-free directory,
only hosting those other dirs)
One of the reasons I am doing multiple virtual servers is because of
the RegEx rules that need to be put in place to perform dokuwiki URL
rewriting. Following the noirbizarre.info tutorial which does this for a
single dokuwiki instance I'll admit to inferring a rationality to this
in order to keep functionality appropriately separated. So since both my
main/ and docs/ will need them, and due to the other content (thing/,
which absolutely does not need the regex rules applied nor does it need
to use PHP), it should be under that separate virtual server domain.
The only trick... how to do what I want in cherokee terms? How do I
get, on the same site:
http://www.site.com/* (serving out of main/ or /, applying
dokuwiki regex rules)
http://www.site.com/docs/* (serving out of docs/, applying
dokuwiki regex rules)
http://www.site.com/thing/* (serving out of thing/, not
applying dokuwiki regex rules, perhaps others)
But as I said, from what I can tell, all rules seem to be falling
through and hitting default. I would expect (again, I'm likely missing
some fundamental understanding of cherokee rules) that if I'm trying to
access main/, it hits the doku.php in the root (which I configured as an
index) and should be happy with that rule...
Any suggestions?
I am not doing any hostname matching in any of the rules (in my
current understanding it currently seems redundant)...
Do I need to have some other way of forcing a match in the rulesets?
Perhaps some "File Exists" rule?
Also--- where can I find a description of the functional implications
of a "Final" vs. a "Non-Final" rule? Would this hold some clue to my
current situation?
And, if I'm trampling over established terminology (I'm more of a *NIX
System Administrator and programmer than Web Server expert), by all
means set me straight on what I'm actually asking for.
Thanks for any help that can be provided.
-Matthew
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
