05-19-2008, 10:35 PM
I'm interested in setting up an add-on domain. I was told that the add-on domain could be placed something like:
[maindomain.com]/public_html/addondomain/index.htm
... and it would appear as:
addondomain.com
... and my existing main domain would remain as:
[maindomain.com]/public_html/index.htm
maindomain.com
I have maindomain defined on my computer as a Dreamweaver site, and while I'm told that I could 'cloak' the public_html/addondomain/ hierarchy so that it would not be uploaded to the web server (when working on the maindomain site), I have concerns that things like global search and replace in Dreamweaver might cause changes in that addondomain subdirectory (off public_html), as well as the same in unix using recursive search and replace, etc., commands.
I asked if perhaps I shouldn't move my maindomain down a directory (both physically, and having its root defined that way in DNS), like:
/public_html/maindomain/
I tried the following:
--
Move the document root by creating a symbolic link in place of index.htm and have it point to the another directory.
# create a symbolic link to point to the location you want (Where XXXX is the name of the directory you created)
ln -s XXXX/index.html ./index.htm
--
Unfortunately that recipe did not work. The home page worked, but none of the links. It appears the only way a symlink would work would be to create a symlink of the web root, i.e., the "~/public_html/" directory, to, say "~/public_html/maindomain/". Is that correct, or would that not work?
Even if it did work, then if I created my add-on site at "~/public_html/addondomain/", I believe that would resolve to "~/public_html/maindomain/addondomain/", in which case I would not have gained anything.
--
New suggestion:
Add an addon domain parallel to my public_html folder.
Click on my add-on domain icon and add the directory next to the house icon (omit the public_html).
Assuming the permissions are correct, then I shouldn't have anything to worry about, is that right?
Bob
[maindomain.com]/public_html/addondomain/index.htm
... and it would appear as:
addondomain.com
... and my existing main domain would remain as:
[maindomain.com]/public_html/index.htm
maindomain.com
I have maindomain defined on my computer as a Dreamweaver site, and while I'm told that I could 'cloak' the public_html/addondomain/ hierarchy so that it would not be uploaded to the web server (when working on the maindomain site), I have concerns that things like global search and replace in Dreamweaver might cause changes in that addondomain subdirectory (off public_html), as well as the same in unix using recursive search and replace, etc., commands.
I asked if perhaps I shouldn't move my maindomain down a directory (both physically, and having its root defined that way in DNS), like:
/public_html/maindomain/
I tried the following:
--
Move the document root by creating a symbolic link in place of index.htm and have it point to the another directory.
# create a symbolic link to point to the location you want (Where XXXX is the name of the directory you created)
ln -s XXXX/index.html ./index.htm
--
Unfortunately that recipe did not work. The home page worked, but none of the links. It appears the only way a symlink would work would be to create a symlink of the web root, i.e., the "~/public_html/" directory, to, say "~/public_html/maindomain/". Is that correct, or would that not work?
Even if it did work, then if I created my add-on site at "~/public_html/addondomain/", I believe that would resolve to "~/public_html/maindomain/addondomain/", in which case I would not have gained anything.
--
New suggestion:
Add an addon domain parallel to my public_html folder.
Click on my add-on domain icon and add the directory next to the house icon (omit the public_html).
Assuming the permissions are correct, then I shouldn't have anything to worry about, is that right?
Bob