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

Obsolete directory entries in OpenDeploy receiver definition

asalim

Hello,

my current OpenDeploy receiver configuration (file: odrcvr.xml) contains for a specific host several path entries (within tag <allowedDirectories>.

As example
<path name="/.../dir1/subdir1">
<path name="/.../dir1/subdir1/subdir2">
<path name="/.../dir1">

I think the first two entries are obsolete. Or could there be a reason for defining those subdirectories separately?

Thanks,
Alexander

Find more posts tagged with

Comments

Faizi

Hello,

my current OpenDeploy receiver configuration (file: odrcvr.xml) contains for a specific host several path entries (within tag .

As example

I think the first two entries are obsolete. Or could there be a reason for defining those subdirectories separately?

Thanks,
Alexander

Hi,
Allowed directories path works in order of relative. If a root directory is defined then the deployment can be done in any of its sub-directories.
As per as your example the single entry
can also perform same thing. But its depend on the deployment config file that how the target area path is set.

Thanks,

Faizi

Hello,

my current OpenDeploy receiver configuration (file: odrcvr.xml) contains for a specific host several path entries (within tag .

As example

I think the first two entries are obsolete. Or could there be a reason for defining those subdirectories separately?

Thanks,
Alexander

Hi,
Allowed directories path works in order of relative. If a root directory is defined then the deployment can be done in any of its sub-directories.
As per as your example the single entry [HTML]
[/HTML] can also perform same thing. But its depend on the deployment config file that how the target area path is set.

Thanks,