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

Should I commit DAM metadata schema into Git codebase?

Avatar

Level 1
What is the best practice for DAM custom metadata schema and custom search forms. Do we commit the /conf/../dam/adminui-extension/metadataschema/.. into Git codebase and deploy through maven into AEM? OR do we treat metadata schema similar to /content and install the package manually on different environments?
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @sarav-sgws,

In my opinion that is a good practice to keep your metadata schema configuration in git repository. I think that this is more application than content part. It's always good to have ability to track history of changes regarding metadata schema structure.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @sarav-sgws,

In my opinion that is a good practice to keep your metadata schema configuration in git repository. I think that this is more application than content part. It's always good to have ability to track history of changes regarding metadata schema structure.

Avatar

Level 1

sounds good. I too believed anything /content/ shouldn't go into git, but all rest folder should be committed. Was checking if there was opinion or reasons for otherwise. 

Will commit and close this question.