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

full deploy, how to save target dirs

nico

So i'm doing a full deployment from a staging area in teamsite, i've set my filters in the deployment in terms of what not to send given that some of the files are still in development, and are not ready to go to test.

However when I do the deployment, od see's those directories that are filtered (because they already reside on the target) and starts deleting stuff in them since they are "missing-in-src".

So this begs the question, is there a way to tell the target what directories should be filtered from deletion?

I know that you can specified allowed directories in the target odrcvr.xml file.

Thanks,
Nico

Find more posts tagged with

Comments

jbonifaci

Filters can be applied on both the source and target. If you are filtering something from the source you don't want to be deleted from the target, you just need to specify the filter in both the source and target. This should be well documented in the OD Admin Guide.

~Jeff

Migrateduser

check transferRules doDeletes="yes" dontDo="no" in your configuration xml and set the flag doDeletes to "no".

however, this is really a useful flag since this way users are allowed to delete the deleted files on a target system which could be a different machine or a webserver alltogether.

regards,
Rahul

jkepler

In other words:

<deploymentConfiguration>
<localNode host="****" />
<replicationFarmSet>
<replicationFarm name="****-farm">
<nodeRef useNode="node-****">
<targetRules>
<filters>
<excludePath subPath="directory_name" />
</filters>
</targetRules>
</nodeRef>
</replicationFarm>
</replicationFarmSet>
<definition name="DEPLOY1">
<source>
<sourceFilesystem area="/source/path">
<pathSpecification>
<path name="path" />
<filters>
<excludePath subPath="directory_name" />
</filters>
</pathSpecification>
</sourceFilesystem>
</source>
etc ...
You can also put the target filter in the target element. It's more useful to put it in the targetRules element if you have multiple targets.