Maintain Versions for Configuration Files

Hi Everybody,

Can someone help with the below scenario.

I am currently using Teamsite 6.7.1 and in the process of upgrading to Teamsite 7.5 version. Currently some of the core confiuration files (.ipl, .pm, .xml etc) we are currently maintaining in the server. If there are any changes required to those files, we will need to take the backup of the existing files and make the changes in the file, I see huge risk here to maintain directly on the server, Instead I would like to keep these files in CMS branch and everytime if I require to make the changes to those files it will keep track of version history. Is there any way to keep the files in Teamsite and whenever if I make any changes, it should directly updates the files in the server i.e G:\Teamsite\ipl\..... Is there any way to implement this without creating any workflows,

Any help is highly appreciated,

Find more posts tagged with

Comments

nipper

Without a workflow, no.

I do it all the time with a workflow. Much better approach because you do not need root access to change.

Only issue is when you really screw something up and TS does not come up or the UI doesn't come up. Then you need to be able to get around it. The 1st is pretty easy, those errors not common. Hosing the UI is certainly possible and that you cna take care of with editions.

David Smith

We also manage many of the TS config files within TeamSite and use a simple workflow to publish the config files to the right locations on the filesystem. Since you haven't done that yet and you're in the middle of an upgrade, you should definitely make a backup of your filesystem prior to the upgrade and be able to go after individual files in the event you mess something up. Once you're stable in 7.5 (good luck if you are using XSLT), then you can start to create a config branch and begin doing it the right way.