another htdocs.

joon

I think "htdocs" is the root folder of Apache server.

I like to make or see another root foler like "htdocs",

The reason is ;

(1) I make and test some of my html or php files in the root(htdocs).

Let's call it "project1".

(2) I add and modify the project.

Let's call it "project2"

(3) I can overwrite the "project2" on the "project1"

(4) However, If I overwrite the "project2" on the "project1".
the "project1" will be completely removed.

(5) Of course, the disappearing "project1" doesn't matter because
I have "project2" the new one of project1.

(6) But when something dissatisfying is found in "project1", I should back to "project1", and start again with the project1.

(7) Storing the former work(project1) used to be good references
in my case.

(8) I can store the "project1" in another folder of my own, but I may will compare the result of "project2" to the result of "project1" continously.

that is why I need another "htdocs".

It might be the concept of "localhost1" and "localhost2"
Anyway, If it's possible, I like to compare "localhost2" to "localhost1" for continous test.

I hope you understand my point.

paul088

Don't see the need for two roots. You can create as many folders as you want under htdocs. Call them, project1, project2, project1_backup, project2_backup, etc. In each folder, you may place an index.php file, and point url to localhost/foldername.

joon

Thank you, Paul for your concern.

But in that case, root path(/index2. php) would not work.
I can't make the paths all in relative path(project1/index..php) and absolute path(http://www.blabla.com/project1/index.php).

For example,

(1) I put each index.php into the folder project1 and project 2.

(2) there is a folder1 in project1.

(3) If a file in the folder1 has a link wrote "/index.php" to move to the index.php in project1, it'll move to the index.php in the folder of "htdocs"(root).

paul088

I may not get your picture correctly. Is it right that you create a project, and you later modify it? Tell me if I am wrong:

You want to keep the 1st version in one folder (folder1), while put the 2nd version in a different folder (folder2). You want to be able to test them simultaneously at some stage, but they are not linked in any way. When you are happy with 2nd version, you move it to folder1 to replace the 1st version. You then start to modify the 2n version that is still in folder2. You then have the 3rd version in folder2. You test both folders, and move 3rd version to folder1 to replace 2nd version. This goes on and on until you get a final version.

Am I right? I want to make sure I understand it before I go further.

joon

Most of your understands are, I think, right.

Anyway, I'll try to explain myself logically.(I am not a native speaker of English).

(1) I have a project.

(2) I make some files and folders for the project.

(3) Basic works of the project is finished.

(4) I named the first work for the project "project01".

(5) I copy all the files and folers in the project01 and named it "project02"

(6) Now I have two projects. one is project01, and the other is project02. they are actually same at the moment because project02 is the copy of project01

(7) I begin to modify project02 and add some other work into project02.

(8) On the way of modifying the project02, I sometimes compare the project02 to project01.

(9) I copy project02 and named project03.

(10) I modify project03, and I sometimes compare project03 to
the project02 or the project03. (Not only the result of the each project but I compare the code).

..............................

(11) I finished project99, and copy it, and named it project100.
(12) I modify project100, add some other concepts into the project100.

(13) On the way of working for project100, I sometimes compare
the project 100 to project01~project99).

(14) I finished the project100.

(15) I think the project100 is near to perfect.

(16) The project is finished.

By the way, my MSN messenger is "joon_star@hotmail.com".
I will be happy if you contact me.

paul088

Ok, I got you. As long as you have folder1-100 (or two folders - one backup folder and one working folder), you are fine with relative url. Treat each folder as root folder, and do not put anything in or link anything to htdocs (real true root folder).

joon

The problem is that I have to use root path for some of my links
because after each project is modified, I should post it
to my rented server.

Everytime I post the modified work to my rented server , I
should change the so many link using relative path into root path.

Anyway, thanks for your concern.

On the way of this posting, I've got a solution for this although it
is not perfect solution.

paul088

Why don't you share your solution with all of us? We may use it someday. I feel bad when someone said "Ok, I found the solution" without telling what the solution was, after so many users had given him or her so many suggestions. Sharing your soltuions is a way to give back to this community (Is this in Buzzly's General bulletin board guidelines? ).

By the way, if your entire project is in a folder on your PC, you can simply transfer the content of this folder (excluding the folder name) to the root directory of your rented server. Can't see why this is not working.