"Now it's time to re-export your configuration in the config sync directory, in order to update the affected YAML files." - How to do?

Created on 4 January 2024, 12 months ago
Updated 11 January 2024, 12 months ago

Problem/Motivation

I've just updated a site from D9.5.11 to D10.2 and Allowed Formats from 2.x to 3.x and run updb.

The final step in "What you need to do?" in the project description is "Now it's time to re-export your configuration in the config sync directory, in order to update the affected YAML files."

As a less experienced user, I'm not sure what that means. How exactly should I do that? I didn't export any config earlier in my update process, and haven't really done config exports before.

💬 Support request
Status

Closed: works as designed

Version

3.0

Component

Documentation

Created by

🇹🇭Thailand Nick Hope

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Nick Hope
  • 🇹🇭Thailand Nick Hope

    So I did this in Drush by running drush cex but, as I understand it from the documentation , I don't think I really needed to do anything at all while my site is only in local development. My sync directory had no yaml files in it. A clarification of that in the "What you need to do" section on the module description would be helpful.

  • You should still always export config even while in your development environment. The reason for this is because config files should be included in commits and checked in to your code repository. Any config files that contain sensitive data or that you want to exclude could be excluded in your .gitignore file and with Config Ignore .

  • Here's a quote from Stack Exchange:

    you probably want to move your config folder out of files (you need to update the path in settings.php) and commit it. You shouldn't only have one environment, and config allows you to make changes on one site, export it and import it on production. There are many questions here and documentations about this available.

  • Status changed to Closed: works as designed 12 months ago
  • 🇹🇭Thailand Nick Hope

    Thank you very much @solideogloria. Your explanation and links help me a lot. As an independent site builder, I don't actually use Git in my local development, relying instead on regularly backing up my codebase and exporting my database. But I probably should!

    Marking this as Closed (works as designed), since the discussion is beyond the scope of Allowed Formats.

  • Being able to see what changed when is pretty important if you notice errors in log messages. It's hard to know what changed around a certain date if you don't have your commits/changes recorded.

Production build 0.71.5 2024