Moving to Cloud Manager deployment, should I get rid of the old /etc/clientlibs/myapps | Community
Skip to main content
Level 6
March 11, 2021
Solved

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

  • March 11, 2021
  • 1 reply
  • 816 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Shubham_borole

@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-restructuring.html?lang=en#introduction as well.

Thanks

1 reply

Shubham_borole
Community Advisor
Shubham_boroleCommunity AdvisorAccepted solution
Community Advisor
March 11, 2021

@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-restructuring.html?lang=en#introduction as well.

Thanks