Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhanced Virtual Hosting: Dynamic Document Root #803

Open
danielniccoli opened this issue Mar 24, 2013 · 0 comments
Open

Enhanced Virtual Hosting: Dynamic Document Root #803

danielniccoli opened this issue Mar 24, 2013 · 0 comments
Labels

Comments

@danielniccoli
Copy link
Contributor

Original author: julesvan...@gmail.com (March 18, 2011 02:53:51)

What steps will reproduce the problem?

  1. Virtual Server: default
    Document Root: /var/www
    Directory Indexes: index.html,index.php
    Keep-Alive: [x] Allow
    Max Upload Size: [Optional]
    Method: Enhanced Virtual Hosting
    Dynamic Document Root: /www/${root_domain}/${domain}
    Check Document Root: [x]

What is the expected output?
Both dirs respectively /var/www and /www/vector.name/vector.name exist. The expected output are the contents of the latter directory.

What do you see instead?
The contents of the former directory. In other words, the dynamic document root is not found and the general document root is used.

What version of the product are you using?
About: Cherokee 1.2.1

On what operating system?
Debian squeeze 2.6.32-5-xen-amd64

Please provide any additional information below.

It has been tested with the template variables: ${domain} and ${tld} which worked as expected, so the problem is with the variable: ${root_domain}.

Since squeeze only supports Cherokee 1.0.8-5 and the ${root_domain} variable was not available in that version, it was desirable to upgrade to a newer version of Cherokee. To the /etc/sources.list has been added the following line: "deb http://ppa.launchpad.net/cherokee-webserver/ubuntu karmic main" followed by an apt-get install.

Extra:
While not interested in mass hosting, there exists a strong wish to mass organize files in a constructive way, preferably using the reverse dns convention in two steps. Let's say: /www/${tld.domainname}/${tld.domainname.*} where * can be substituted by subdomainnames any level deep, so I would suggest respectively a ${root_domain_r} and ${domain_r} where the postfix _r means reversed dns notation.

Original issue: http://code.google.com/p/cherokee/issues/detail?id=1159

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant