Archive TeamSite

DavidMusser

Everyone,

I'm looking for a fairly simple way to backup my iw-home directory for teamsite, and store it in teamsite. So right now I've only got it setup for teamsite, not OD, but wanted to see what people thought of these two configurations. The first is for pulling from iw-home and the second is for putting back. The idea being that I would edit config files in teamsite and push it to production using OpenDeploy.

I'm using excludes and includes... I do not have do deletes on at this time, but am thinking of doing that since the only directory that I am deploying everything from is the customer_src directory... the rest are just includes of .cfg, .xml etc.. I need to check to see if any of the files are being written to while TS is active... Also I've got the big ones.. .xml, .tpl etc... check the file to see if I need to add any others... I can't think of any at this time...

The put it back version I'm using the pattern substitution so that I can replace the area with that of an edition... If there are files that are being written to by the application I may modify the put back to be a file list deploy of what's modified... but wanted to see what the group thought.

Let me know what you think.. if you think they are good, bad, that the server will blow up killing everyone in the room etc...

13adam13

David,
I have in the past used TeamSite to store teamsite files, andI thought it worked really well.
My was an act of necessity, because I was a contractor developing teamsite on Unix, and the Unix admins would not give me root, and at the time Interwoven was not prepared to tell me what files did not need to be owned by root. Since OD runs as root (or at least I told them it had to), it was able to update config files and such without too much issue.

I did not have do_deletes on for the Od because of the way that I managed the files. When I first started off, I tried putting all TeamSite files in the Admin branch, but found this to be combersome, and I was always anquis that I was going to kill something that I should not have killed.
Instead, I pulled any files that I was working on into the workarea, made my changes and then deployed. This process seemed to work pretty well, and was the same that I used when updating teamsite with patches.

Because I was making editions in teamsite for every change, I had a higher level of comfort that if I broke something, I could quickly fix it. Also, when there was a patch release, I could check the files histories and merge any changes that I had made to Interwoven files.

I think that not only is this a good idea, but that Interwoven should develop a development server that integrates support for this kind of thing. It would know when you needed to restart the Od reciever or iwreset the teamsite interface, instead of forcing me to try to parse the log files and figure it out myself.

--Adam Wilson
Senior Programmer