DS-IRM (Domain Stack-IRM, or Subdomain)

[Gerrit]

I'm a bit confused about your DS-IRM-order-form. It says:

"Points to: /big/dom/xusername/www"


Does this mean I could select:

/big/dom/xusername/subdomain/

... as well as:

/big/dom/xusername/www/subdomain/

???
This would be great because the directory wouldn't be accessible via username.com/subdomain then ... but I always thought it has to point to a subdirectory within the www-directory!?


Smile!
Gerrit

[Jake]

This thread might be useful:
http://www.aota.net/forums/showthread.php?threadid=10445

It doesn't really answer if username.com/subdomain is accessible or not though and I can't answer that either.

HTH,
Jake

[Gerrit]

Thanx for the hint. But the thread doesn't clarify if a subdomain can be mapped to:

/big/dom/xusername/subdomain/

Smile!
Gerrit

[Terra]

To lead off, have you read our Online Docs at:
http://www.futurequest.net/Services/IR/

I'm a bit confused about your DS-IRM-order-form. It says:

"Points to: /big/dom/xusername/www"
Technically, that is a DS:IRO since a request for:
http://foo.example.com/

will be the same as requesting:
http://www.example.com/

since they both pull files from the same DocumentRoot...

Does this mean I could select:

/big/dom/xusername/subdomain/

... as well as:

/big/dom/xusername/www/subdomain/
The 'Points to:' section of the order form gives you a starting point, so that you can fill in where you want it to go to...

DS:IRM *must* point to a directory contained within the 'www/' tree...

e.g.:
http://foo.example.com
/big/dom/xexample/www/foo
or whatever

However, this won't work:
/big/dom/xexample/foo

The Order Form will error out as displayed below:
Error:
An error has occurred:
The subdomain directory must be in the "/big/dom/xexample/www/" directory.

Hope this explains the Ordering requirements for the DS:IRM....

--
Terra
--Easy to understand in concept, but difficult to explain without writing a book--
FutureQuest

[Jeff]

This would be great because the directory wouldn't be accessible via username.com/subdomain then ... but I always thought it has to point to a subdirectory within the www-directory!?
Can't you just select a cryptic subdirectory for the subdomain to point to?

For example if you pointed three.yourdomain.com to /www/subdomthree/ I don't think anyone would accidentally hit that.

With IRM's I started by keeping it simple, for example having yachtdesign.info point to boatdesign.net/yachtdesign. But then I decided that I wanted to have more flexibility, so new IRM's I mapped using the full extension since this would be unlikely to be a directory I would ever want to not be the other site, for example boatdesign.net/yachtdesigninfo or /boatdesign.net/yachtdesign-info or even boatdesign.net/IRMyachtdesigninfo)

If I did ever in the future want to share files, I can always sym link that (ln -s IRMyachtdesigninfo yachtdesign) to create an easily accessible subdir of the main domain which leads to the same content as the secondary domain.

But no one is likely to guess it if you don't want them to. Hope I didn't ramble on too much...

[Gerrit]

Thanx! Now I know.

Of course I've read the IR-service-page. The confusion occured when I saw the full directory path within the ordering-form.

Smile!
Gerrit

[Gerrit]

Is it possible to stop http/analyzer to count anything that's happening within the subdomains-directory?

Smile!
Gerrit

[Terra]

No, I'm afraid not...

--
Terra
sysAdmin
FutureQuest