Newbie questions about committing changes.

[jmb]

Apologies in advance for this newbie post, but I'm stumped...

I am new to SCC programs, Vault is my first attempt at formal source code control, so please bear with me.

I installed Vault and I think I have it running correctly so far. I have a server (Win 2k server) and a 1 client machine.

I have successfully created users and a repository, and I am able to check out files, edit them and check them back in with no errors.

Here is my problem:

After I check in the updated files and reconnect to my web app (on the server) I do not see the changes. I am making very obvious changes to the pages (adding text) so the changes should be visible once the page loads. Yes, I hit refresh, I even went so far as to reboot both machines. But no changes show up.

But if I checkout the files again and look at the source the changes I checked in are still there.

If I do a search on the server for the filename I updated I cannot find it (I see the original in inetpub folder, but no newer versions)

Where can I find the location of my checked-in files? I couldn't find anything in the documentation.

I thought the process was:
1) Create a repository (pointing to the folder with the live code)
2) Check out the page I want to update
3) Make changes to file
4) Check-in with comments
5) View new page on server

I can do all of the above, except for see the actual changes.

Do I need to do something else to make my changes live after I have checked them in?? Am I missing a step?

[lbauer]

When you checkin files, the changes are stored in the Vault database, in MS SQL Server. If you want physical copies of the files in a particular folder or location, you'd need to do a Get with a client, or use Shadow Folders.

For instance, you can run an automated script using the Vault Command Line Client to do a get periodically to the directory of your choice.

Many users who are updating web sites use Shadow Folders. A Shadow Folder is a directory that's automatically updated with the latest changes from database folder that's being shadowed. Shadow folders must be on the same LAN as the Vault Server.

You can configure Shadow Folders in the Vault Admin Tool under Repository Options->Configure Shadow Folders. For details, see Vault Admin Help->Reference Guide->Dialogs->Configure Shadow Folders.