Migrating to Cloud Manager (with AMS) what to do with /etc | Community
Skip to main content
fionas76543059
Level 6
Jan 8, 2021 4:19 PM UTC
Solved

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

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.
Ankur_Khare
Ankur_KhareAccepted solution
New Participant
Jan 8, 2021 5:12 PM UTC

Try keeping them under apps/urproject folder.

View reply

12 replies

fionas76543059Author
Level 6
Feb 15, 2021 12:10 PM UTC
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.
Translate
fionas76543059Author
Level 6
Feb 15, 2021 11:48 AM UTC
I added the /conf/... path to SlingAuthenticator sling.auth.requirements parameter with a "-" in front . Didn't seem to help though.
Translate
fionas76543059Author
Level 6
Feb 15, 2021 11:45 AM UTC
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.
Translate
joerghoh
joerghoh
Employee
Jan 10, 2021 5:20 PM UTC

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.

Translate
    Kunal_Gaba_
    Kunal_Gaba_
    New Participant
    Jan 11, 2021 3:59 AM UTC
    We tried moving the component design dialog stuff to /conf but it didn't work. We have not yet migrated to editable templates yet and therefore we will have to continue with the design dialogs. Also, if we keep the design in /etc then how we can activate the design as there is no miscadmin UI and I could not find any Touch UI equivalent.
    Translate
    praveenjain
    Level 3
    Jan 10, 2021 3:16 AM UTC

    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

    Translate
      Ankur_Khare
      Ankur_KhareAccepted solution
      New Participant
      Jan 8, 2021 5:12 PM UTC

      Try keeping them under apps/urproject folder.

      Translate
        Shashi_Mulugu
        Shashi_Mulugu
        New Participant
        Jan 8, 2021 5:09 PM UTC

        @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.

        Translate
          fionas76543059Author
          Level 6
          Jan 8, 2021 9:11 PM UTC
          Thanks for your swift response ! Ankur sugged to put them under apps so I'll try that.
          Translate
          Terms & ConditionsAccessibility statement

          Loading footer...