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

filelists and path specificiations

Johnny

Hi Guys,

OD version: 5.6.0.1.0 Build 21220

Im trying to get my head around specifiying various paths while using filelist deployment.

What im trying to do:

With the usual area deployment, I can specify an area, say

<sourceFilesystem area = "y:\default\main\branch\STAGING" >

and then use a series of path specifications to wire up various source directories to different target directores, say

<pathSpecification>
<path name = "htdocs"/>
<targetRules area = "e:\data\htdocs\intranet"/>
</pathSpecification>

<pathSpecification>
<path name = "apps\installableapps"/>
<targetRules area = "e:\appserver\installableapps" />
</pathSpecification>

Because we have numerious sites with some using different technologies/directory structures, what I would like to do is use a filelist deployment with a generic deployment script that will create a filelist starting from the area eg

htdocs/index.shtml

then let the deployment profile take care of what should go where.

Being a generic deployment script for all areas, it would probably be easiest to create one definition with one sourceFilesystem filelist.

Ive had problems doing this with filelists, as it seems you cannot specify path names that are used in the flielist. From what I can see, when using filelists, the deployment must send the whole directory path as specified in the flielist and cannot be chopped up with path name specifications.

Is this correct, or am i doing something wrong...? Is there a better way to solve my requirement?

Thanks!

John Cuiuli

Find more posts tagged with

Comments

Johnny

has anybody got something to share?...?

John Cuiuli

Adam Stoller

I would not try to force a generic solution on a non-generic environment like this.
Either you convince folks that the structure needs to be consistant across all branches / between source and target sides - or you develope specific configurations for specific environments.

Anything else and you'll probably be spending way too much time on it.

The only alternatives I see are:
1) having a wrapper script that can perform the logic to break the list of files into N filelists - and passing different filelists in as parameters for different sourceFilesystem directives [rather than pathSpecification directives]
2) Using a much more generic sourceFilesystem area specificiation [e.g. /default/main] and more explicit filelist entries [e.g. /www/STAGING/somedir/somefile.html] - and then using filters in all of your pathSpecification sections to determine which files fall into which pathSpecification directives.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Johnny

Thanks for your post fish.

It looks as though you will be right. I thought the best option would be to have everything as generic as possible, and all custom stuff would be in the deploy profiles with path specifications.
The only problem i ran into was the way filelists changes the way path specifications are treated. There wouldnt really be much more work other than that.

There's been a slow transition from an older directory structure to a new one. Throw in a change of technology in some sites, it will be a while before all branches will be using the same structure.

John Cuiuli