CODEWITHSUNDEEP
svntortoisesvn
Jude Cooray
Jude Cooray

Reputation: 19872

TortoiseSVN - Checking out to multiple directories?

I am very new to Tortoise and SVN's in general. I currently have a PHP project that I need to add to a SVN repository. I already had a checked out folder and i added the project to that folder and committed. So everything is cool.

But i just realized that I need to have the PHP project in my wamp folder's wwwroot to actually test it. I can copy and paste the folder to the wamp folder and then do the changes and replace the files back, but it is too cumbersome.

So what I want to do is actually checkout the same folder again from the repository to the wamp folder as well and keep working there and commit the changes which is MUCH easier!

Will this cause any trouble by having two copies? Is this is the correct way to handle it?

Upvotes: 1

Views: 404

Answers (5)

splash
splash

Reputation: 13327

Create a link (mklink or Junction) from your project folder to your WAMP folder. This way you don't need to checkout it twice.

Upvotes: 0

Christian Severin
Christian Severin

Reputation: 1831

You can keep as many SVN repository copies on your client machine as you want. However, if you plan on mainly working on the files in your wwwroot folder, I suggest you delete the other SVN folder to keep things simple. Otherwise you WILL at one point forget to syncronise the two, resulting in lost work and possibly long bughunts...

Upvotes: 1

Shamim Hafiz - MSFT
Shamim Hafiz - MSFT

Reputation: 22114

From my experience, I would say it won't cause any problem.

Since this is PHP project, your working code and the code on server will be same, except few configuration files.

However, considering development in general, it is better to give a build rather than directly synchronizing code from the repository into the live folder. For PHP projects, the build is very simple, simply copy entire folder to www directory. For projects, developed using other technologies, you may need to compile the code and make major changes to the settings.

Therefore, it is better to leave the code in the www folder as it is, and only update it with a build, rather than direct update from SVN repository.

Upvotes: 0

Arsen Mkrtchyan
Arsen Mkrtchyan

Reputation: 50752

Yea, it will and that is the correct way

Upvotes: 1

Hamish
Hamish

Reputation: 23346

No it won't cause any problems, in fact this is exactly the sort of thing SVN is designed to handle! Just remember to update your www version if you commit changes to the other one, and vis versa.

Upvotes: 2

Related Questions