Use drush config import/export instead of features

[der-On]

Using the features module to store config as code was required in Drupal 7 but in Drupal 8 importing and exporting config using drush is way more robust and straight forward.

However removing features and the modules storing the config is not as easy, as it all is cyclic dependent on each other. In the develop branch we have all that features stored in modules within config files. Now it is time to create a strategy of savely removing features and the generated config modules.

[FlxAlbroscheit]

Hi @der-On ;) I have successfully activated drush import/export on our staging system. In the next days we plan some minor modifications of the maps generated by views module. Afterwards I will spell a "feature freeze" on the master-branch and merge the configurations of our live system into the develop-branch sync-folder (only those parts which have changed in the last couple of weeks). The "exciting" part will then be to evaluate how we can fully remove the feature-modules; I hope it will be enough to remove all dependencies/references on le_*...

For now, is there anything I can do to assist you with this ticket?

[der-On]

@FlxAlbroscheit Thank you for your work on this. I will look into the le_ modules and will try to remove them as possible, as everything is already stored in the config. If I encounter problems I'll let you know.

I might merge le_core with my le_webbuilder and le_admin into a single custom module with a better structure, so we have a less scattered and more streamlined codebase.

[FlxAlbroscheit]

I will re-use this ticket for the soon-to-start merge of develop-branch into main-branch. My list of todos is as following:

• Merge main into dev, regenerate composer.lock
• Export config from live-system, merge into dev-branch (mainly le_*.view.yml - & .metatag.yml- files, as these have changed tremendously since the last fork)
• Edit templates and views in a way that le_akteur- & le_event-image is taken from the new media-field (not image-field as currently)
• Get rid of feature-modules (remove from file system, remove any reference in configurations, profile, custom modules, themes, etc.)
• Check whether custom profile is still required at all (was used only for step-wise installation of feature-modules)
• Ensure that installation process succeeds without problems
• Ensure that no sensible data is leaked to the config-files (API-keys, default-site-mail, etc. -> .gitignore!)
• Update documentation (main README -> split into INSTALL_APACHE, INSTALL_DOCKER)
• Merge dev into main
• Ensure again that installation process succeeds, make release and publish
• Profits

On installation/upgrade of live-system (after according test-run on staging system):

• Backup, backup, backup!
• Enable maintenance mode
• Run image-to-media-field script
• Pull main-branch, Run composer install, import & validate configuration
• Update API-keys (Matomo, reCaptcha-replacement)
• (If necessary:) Add missing German i18n strings, evtl. push back to git
• Disable maintenance mode