nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deploy to itself?

jmcdonald

Is it possible to create an Open Deploy configuration to deploy files on an OD server to itself?

We would like to use Interwoven Teamsite to manage the configuration files, then deploy to itself....

ie:
source: y:\default\main\{config branch}\etc
target: c:\iw-home\etc

I'm running into trouble because I think the deploy.cfg file will only let you configure an OD server as a sender or receiver (not both)

Find more posts tagged with

Comments

Dwayne

It is certainly possible to have an OD base server deploy to itself. The test deployment, test.xml, does exactly this. Take a look at it as a reference.

I've done this numerous times to manage TS (and OD) config files within TS, and then deploy them with OD. Allows people without login access to the server to manage/version/deploy config files.

--

Current project: TS 5.5.2/6.1 W2K

jmcdonald

Is an ODRCVR.XML file required?

Dwayne

Nope. odrcvr.xml is only for a receiver. odbase.xml is for a base server, which is also, by definition, a receiver. There is nothing a receiver can do that a base cannot also do.

Just put the entries that you'd have in your odrcvr.xml into odbase.xml.

--

Current project: TS 5.5.2/6.1 W2K

jmcdonald

It works! Thanks for the help.