Massage target Path on the fly

Can I set OD configuration so that asset's source Path is modified to reflect
target's deeper nesting? Modification is consistent and can be done with a simple regex.
To illustrate, resource "...root/page/abc" deploys to "...root/page/CMS/TS/abc".

Is it possible to achieve by configuration only, without any coding?
( I do realize that there are quite a few workarounds. I can for example do DNR "source, before", build temporary
structure on the fly and deploy from there, etc...That's not the question)

Tips, hints, RTFMs appreciated.

Find more posts tagged with

Comments

iwovGraduate

You can't use regex on the source/target paths the way you explained. You can break down the deployment in separate definitions to allow different target directory for each definition. Although I doubt if thats what you are looking for.

ISCBorisB

You can't use regex on the source/target paths the way you explained.

Thanks. I've reached the same conclusion, eg it can not be done the way I wanted it.

You can break down the deployment in separate definitions to allow different target directory for each definition. Although I doubt if thats what you are looking for.

Right again. In my case root re-mapping using *Target per Definition* approach boils down to 180 Countries x 1.5 Languages ~ 270
Definitions per Deployment type. Oh, well...