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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM cloud: which directories needed to sync content between envs via packages?

Avatar

Level 8

We create the content on production, then sync the content down to UAT / test / dev cloud AEM envs.

 

The problem is that its easy to miss items (such as policies), or take too much (and cause issues).

 

We tried the following:

 

/content/our-web
/content/dam/our-web
/content/experience-fragments/our-web
/conf/our-web

 

as /conf/ourweb contains several important dirs, including templates, template types and policies.

 

However, when we try to deploy the above package to another of our envs, we get:

 

"Package (or it's subpackage(s)) contains application content which isn't supported at runtime."

 

Any suggestions on directories we should and should not include as part of a complete content sync package?

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @TB3dock 

 

The paths look fine. Can you check 

  1. If there are any spaces in the filters
  2. If there is any empty path
  3. Any error that you see in the log

Thanks,

Kiran Vedantam.

View solution in original post

0 Replies

Avatar

Correct answer by
Community Advisor

Hi @TB3dock 

 

The paths look fine. Can you check 

  1. If there are any spaces in the filters
  2. If there is any empty path
  3. Any error that you see in the log

Thanks,

Kiran Vedantam.