Translating Source Paths to Target Paths

djtangman · 2007-07-06T21:28:35+00:00

Can OpenDeploy translate /dirA/subA/*.* to /dirB/*.*. Right now it seems like OD can only deploy /dirA/subA/*.* to /dirA/subA/*.*. Thanks ahead of time.

djtangman

Can OpenDeploy translate <source-area>/dirA/subA/*.* to <target-area>/dirB/*.*. Right now it seems like OD can only deploy <source-area>/dirA/subA/*.* to <target-area>/dirA/subA/*.*.

Thanks ahead of time.

Find more posts tagged with

Comments

Adam Stoller

Can OpenDeploy translate <source-area>/dirA/subA/*.* to <target-area>/dirB/*.*. Right now it seems like OD can only deploy <source-area>/dirA/subA/*.* to <target-area>/dirA/subA/*.*.

Thanks ahead of time.

I'm not sure I understand the question - what do you mean by "translation"?

You have a source area, a path specification and a target area.

All files to be deployed from the source area/path will be deployed to the target area.

If your source area is /dirA/subA and your path is "." and your target area is /dirB/ - the all files and directories within /dirA/subA (that are intended for deployment) will be deployed to /dirB/

djtangman

Yes, exactly, that is what I would have expected: you specify a source and it's path, then you deploy to the target at a specified path. The source path should not be preserved at the target, but in fact, that is exactly what is happening.

Pouring through the OD reference, I can't see a thing I'm doing wrong, but either I am, or OD cannot do what I need it to do. (I assume that the problem is on my end).

I have attached the OD deploymentConfiguration -- see any problems? I just want everything under "assets" copied to the "assets" folder at the target, but I want everything under "html/insight" copied to the target root, not a "html/insight" folder at the target.

Should be easy, right? Maybe it is and I'm just getting caught up in some obscure syntax.

Thanks ahead of time.

Adam Stoller

Yes, exactly, that is what I would have expected: you specify a source and it's path, then you deploy to the target at a specified path. The source path should not be preserved at the target, but in fact, that is exactly what is happening.

Pouring through the OD reference, I can't see a thing I'm doing wrong, but either I am, or OD cannot do what I need it to do. (I assume that the problem is on my end).

I have attached the OD deploymentConfiguration -- see any problems? I just want everything under "assets" copied to the "assets" folder at the target, but I want everything under "html/insight" copied to the target root, not a "html/insight" folder at the target.

Should be easy, right? Maybe it is and I'm just getting caught up in some obscure syntax.

Thanks ahead of time.

Well - a lot might depend on what you're passing in as parameter values for:

"/> ... </pathSpecification> </filelist> </fileSystem> </source> ... </definition>

Ambuj

Yes, exactly, that is what I would have expected: you specify a source and it's path, then you deploy to the target at a specified path. The source path should not be preserved at the target, but in fact, that is exactly what is happening.

Pouring through the OD reference, I can't see a thing I'm doing wrong, but either I am, or OD cannot do what I need it to do. (I assume that the problem is on my end).

I have attached the OD deploymentConfiguration -- see any problems? I just want everything under "assets" copied to the "assets" folder at the target, but I want everything under "html/insight" copied to the target root, not a "html/insight" folder at the target.

Should be easy, right? Maybe it is and I'm just getting caught up in some obscure syntax.

Thanks ahead of time.

Yes, It is easy. Write two different deployment configuration for "asset" and "insight". Pass parameters accordingly and you can have two different target destinations as per your requirement.

I hope it works.

djtangman

Thank you very much for your insights! I hope that one day I can return the favor to you both.