Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Moving to Cloud Manager deployment, should I get rid of the old /etc/clientlibs/myapps

fionas76543059
Level 4
Level 4

hi Guys,

I'm moving to Cloud Manager deployment soon ( 6.5, Adobe Managed Services).

My old clientlibs are in /etc/clientlibs/myapp and my new ones are in /apps/myapp/clientlibs.

As part of the deployment to Cloud Manager, am I supposed to remove the old ones

manually with the package manager ? (Or do they automatically get removed?)

thanks

Fiona

1 Accepted Solution
snbaem
Correct answer by
Community Advisor
Community Advisor

@fionas76543059 

I think you can dereference clientlibs pointing to /etc in your custom code. For removal the code should not have anything building from /etc/clientlibs and filter.xml if any can also control the restriction of etc/clientlibs and just have the clientlibs at /apps level.

 

If the files are there under /etc/clientlibs I this it should be safe to package and remove manually. Other option to try is explore using filter.xml to replace everything from code to instance on deployment and keep nothing in code for etc/clientlibs. That should hopefully clear the clientlibs data under etc. Try these out in local first I suppose.

See https://experienceleague.adobe.com/docs/experience-manager-64/deploying/restructuring/repository-res... as well.

Thanks

View solution in original post

1 Reply
snbaem
Correct answer by
Community Advisor
Community Advisor

@fionas76543059 

I think you can dereference clientlibs pointing to /etc in your custom code. For removal the code should not have anything building from /etc/clientlibs and filter.xml if any can also control the restriction of etc/clientlibs and just have the clientlibs at /apps level.

 

If the files are there under /etc/clientlibs I this it should be safe to package and remove manually. Other option to try is explore using filter.xml to replace everything from code to instance on deployment and keep nothing in code for etc/clientlibs. That should hopefully clear the clientlibs data under etc. Try these out in local first I suppose.

See https://experienceleague.adobe.com/docs/experience-manager-64/deploying/restructuring/repository-res... as well.

Thanks

View solution in original post