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; } } }

OD Admin, without teamsite server

System

Hi,
We are planning to install OD Admin on our Test Server(We dont have/need TeamSite on this) and deploy the content to a production server(Which has receiver). Basically we want to use the OD to deploy some directories under a source directory /opt/path/to/source to /opt/path/to/destination.
Our requirement is to deploy only tested content from source to destination. Lets say we have 100 directories under source and out of which we only need 10 directories (tested) to be deployed to destination. Is it possible to select the directories and deploy them ?. If I have source file system as /opt/path/to/source then it will deploy all 100 directories...or atleast it will try to compare...(these are quite big directories). Thats why we need to deploy only tested content. Please let me know if there is any way out to deploy only specific directories.

One more constraint is our OD users will not have direct access to the file system so they cannot move the tested directories to a location like "tested".

Any help appreciated.
Thanks in advance,

Find more posts tagged with

Comments

Migrateduser

Sounds like you want to select and deploy files from a UI.

The OpenDeploy Admin UI does not provide this capability, but the ControlHub add-on product does. (ControlHub adds versioning and workflow support to OpenDeploy.)

Alternatively, you could write a basic app that generates a file list and then calls OpenDeploy to execute the deployment.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

Hi Todd,
Thanks for your reply. Filelist sounds great idea. Can I have directory names in the file list ? I need to deploy directories.

Thanks,

jbyork

Directory names in the filelist should work just fine.

In your scenario, in the OpenDeployUI, you "could" manually update the OD configuration (XML file), adding the tested directory paths in the filelist section in the XML. Then just launch the deployment using that deployment config. from the OD UI.

It's not as easy as selecting which directories to deploy, but the end result will be the same. You can just update (or create) the OD config (containing the filelist) before you deploy, then just run the deployment using that config.

Migrateduser

A variation on this theme is to parameterize your deployment config. Then you can pass in things like filelist name and target area as parameters when calling the deployment. Parameters are key=value pairs that can be passed in via the OpenDeploy UI or through the -k flag on the command line.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com