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

Filelist Based Deployment - Help

maddy

I have the following branching structure in teamsite -

assets
images
a.jpg
b.jpg

My destination folder structure is -

images
a.jpg
b.jpg

I'm using file list based deployment wherein filearea and filelist path are passed as parameters to deploy task in the workflow.

My filelist.txt consits of entries like assets/images/a.jpg

Issue - I need to get rid of assets folder while deploying to destination and only its files should get deployed mentioned in filelist.txt

As of now it creates a parallel folder in destination at the same level as images.

Any resolutions?

Find more posts tagged with

Comments

vpatel

Technically this is possible and it is relatively easy to do. You probably need to create/update your "deployment" configuration for your "asset" directory.

What is the reason for doing this? Doing such thing will cause some other issues if you aren't already aware of them. For example, if you have any DCRs that reference any of these images, you'll have "asset" in the path which will work fine on the TS Preview side but that path will be invalid in your production area. Something to think about. This is just one example -- make sure you cover all your bases before doing this.

maddy

This is required by the application since teamsite is deploying the content directly into their readable folder heirarchy.

To avoid them to change their code - we planned to replicate the similar structure in teamsite for all assets to avoid this.

As I'm aware this was quite easy to implement in directory based deployments, but unable to figure out it in filelist based deployments.

Can you please send me the resolution to be made in configuration script. I have tried several filters but they aren't working.

ISCBorisB

This is required by the application since teamsite is deploying the content directly into their readable folder heirarchy.

To avoid them to change their code - we planned to replicate the similar structure in teamsite for all assets to avoid this.

As I'm aware this was quite easy to implement in directory based deployments, but unable to figure out it in filelist based deployments.

Can you please send me the resolution to be made in configuration script. I have tried several filters but they aren't working.

File List is a List of entries relative to source File Location.

So, in the Deployment Configuration you can (for example) change your List Source Area from ".../boo"
to ".../boo/assets" and modify File List Entries from "assets/images/a.jpg" to "images/a.jpg".

Same rule applies to the target. Deploy to to "...foo", not "...foo/images". In the latter case the target
will become ".../foo/images/images", not what you want.

As already noted by Vpatel you have to be aware of unintended consequences of moving relative root up/down in
the hierarchy, it may require additional Deployment tuning as well.