Should I commit DAM metadata schema into Git codebase? | Community
Skip to main content
S
saravana_sgws
New Participant
August 16, 2022
Solved

Should I commit DAM metadata schema into Git codebase?

  • August 16, 2022
  • 1 reply
  • 826 views
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?
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 lukasz-m

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

1 reply

lukasz-m
lukasz-mAccepted solution
New Participant
August 17, 2022

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

    S
    saravana_sgwsAuthor
    New Participant
    August 18, 2022

    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. 

    Terms & ConditionsAccessibility statement

    Loading footer...