Topic: Virtual host or something else?

[rumble]

Hi!

I want set up the following structure:
staging.mydomain.com/client/projectname
production.mydomain.com/client/projectname

For new projects i create the following folders in my /home/-folder:
"clientname"-folder which contains "projectname"-folder

I have made a file that I enabled with "a2ensite" including the stuff within the code-block.

It is working fine with clientA for "production" and "staging", but of course clientB wont work, since its something like overridden by clientA, right?

Please help me out.

[James Blond]

Why do you have that Aliases inside?

[rumble]

I thought they would just be affected if the virtual host match?
Im sure this whole config file is setup wrong by me, but any suggestions how I can make the whole thing work with my following structure;
http://staging.mydomain.com/clientA/projectA points to /clientA/projectA/staging, and http://staging.mydomain.com/clientB/projectA points to /clientB/projectA/staging and so on....?

[James Blond]

Now I see the mistake. I was bit blind.
The second vhosts override the first vhosts.

you can't have the same server name twice.

correct would be

[rumble]

yes! that's working correct, but it leaves me with the following issues;

1. i have to manually insert a new alias for each client. Is it possible to do something like a AliasMatch with regexp or something?

2. the document root will be /home/mysite no matter what the matching url is, not a big issue, but is there a way to control so the document root will be /home/clientA/projectA/staging for example?

3. if the user visits staging.mydomain.com the will be able to list the directories, guess you can deny directory listing for that folder, but what about next level? If the user enter staging.mydomain.com/clientA, then I don't want it to be a valid route, more like a "File Not found" or something like that?

[James Blond]

Maybe with AliasMatch
see http://httpd.apache.org/docs/2.2/urlmapping.html#user

[rumble]

will take a look at that then...

but what about my 3)-issue? how can i solve that?

[James Blond]

Use Options -Indexes to prevent that. Or put an empty index.htm into it

[rumble]

Well, of course thats an option, but it feels like there is a better and more correct way to do it?

[James Blond]

Options -Indexes is the most correct way to disallow Directory Listing. If there is a "most correct" thing.

[rumble]

yes, I mean, im totally fine doing it for the root-folder. But what I mean is that you don't want a user to be able to figure out the structure when entering staging.mydomain.com/client because they then get a "403/forbidden"-message, instead of a "404-message", you see what I mean?

[James Blond]

Than use more subdomains. Like staging.clientA.mydomain.com and production.clientA.mydomain.com

But with an Alias like Alias /clientA/projectA
entering just /clientA will give a 404 since that path does not exist.

[rumble]

Hehe, okay. Lets take this from the beginning!

I want to do the following:

For each new project I will create the following within the /home/clients-folder:
clientname-folder and within that a projectname-folder.

When user enters staging.mydomain.com/clientname/projectname, I want to load everything from the clientname/projectname/staging-folder. And if possible I would also like to set so the "DocumentRoot"-folder is now showing /home/clients/clientname/projectname/staging, and also I want error-logs from Apache to be stored in a /home/clients/clientname/projectname/staging/logs-folder.

If the user visits only staging.mydomain.com I would like to either show a 404-message, or a 403-message. Also if the user visits staging.mydomain.com/clientname it should show a 404-message, not a 403-message since then someone can figure out the structure of the folders.

And I know I can setup different virtual hosts for each subdomain, but that will make it look sloppy in my opinion.