Migrating to Cloud Manager (with AMS) what to do with /etc | Community
Skip to main content
F
fionas76543059
Level 6
January 8, 2021
Solved

Migrating to Cloud Manager (with AMS) what to do with /etc

  • January 8, 2021
  • 7 replies
  • 2848 views

hi guys,

I'm doing  the above migration (we have 6.5)  and I have moved the /etc/clientlibs to the ui.apps as required.

 

I have a bunch of other custom stuff in a directory called /etc/<our site> 

These are some "Pages" that contain configuration used by some of our components i.e. not ordinary pages for Editors to use. Also some files used by the robots/sitemap etc

 

My question is :

Is it o.k. to leave them in /etc/ ?   I know that Adobe seems to be encouraging people to stop making /etc a catch-all place for random stuff.

 

I don't want to move them to /content because they mess up the sites page.

 

Any ideas?

 

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 Ankur_Khare

Try keeping them under apps/urproject folder.

7 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
January 8, 2021

@fionas76543059 i think it is ok to keep stuff in /etc untill they are identified by Adobe to be moved to a different location such as clientlibs, designs to /apps, workflows to /conf etc.

    F
    fionas76543059Author
    Level 6
    January 8, 2021
    Thanks for your swift response ! Ankur sugged to put them under apps so I'll try that.
    Ankur_Khare
    Community Advisor
    Ankur_KhareCommunity AdvisorAccepted solution
    Community Advisor
    January 8, 2021

    Try keeping them under apps/urproject folder.

      P
      praveenjain
      Level 3
      January 10, 2021

      For customers with existing code bases, it is critical to go through the repository restructuring exercise described in AEM documentation to ensure that content formerly under the /etc is moved to the right location.

      https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/overview.html?lang=en#osgi-configuration

       

      -Praveen

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        January 10, 2021

        Hi,

        I would not move stuff to /apps, because that's normally read-only and not writeable (except for administrator group by default); in AEM as a Cloud Service it's not writable at all during runtime.

        If your configuration is supposed to be changed during runtime I would store it either in /content or /conf.

          F
          fionas76543059Author
          Level 6
          January 11, 2021
          Thanks Jorg. In fact, we don't change them during runtime. Mostly they are internal lists and a few email templates, robot files etc. and a page of "paths" - servlet resource type mappings. Maybe it was originally thought that they would be changed on-the-fly. They all have primary types cqPaths, but don't really render. I will try putting them in /apps and see how I get on.!
          F
          fionas76543059Author
          Level 6
          February 15, 2021
          hi folks, I moved some stuff from /etc/ to /conf. It is a "Page" with nodes of resourceType of various servlets. However, although the servlets are called fine in Author, in publish there are 404s.
          F
          fionas76543059Author
          Level 6
          February 15, 2021
          I added the /conf/... path to SlingAuthenticator sling.auth.requirements parameter with a "-" in front . Didn't seem to help though.
          F
          fionas76543059Author
          Level 6
          February 15, 2021
          If I explicitly give read permission to anonymous to the page in /conf, it does seem to work. I am not sure how the SlingAuthenticator fits in, I'll try throwing it away and see if makes a difference.
          Terms & ConditionsAccessibility statement

          Loading footer...