Locally cache lakedrops config files
We currently download the config files every single time from GitLab when composer is being executed. This should be avoided by caching those files locally. But we should also have a cache clear mechanism.
We currently download the config files every single time from GitLab when composer is being executed. This should be avoided by caching those files locally. But we should also have a cache clear mechanism.
added Doing label
assigned to @jurgenhaas
changed the description
mentioned in commit ef6ef20e
mentioned in commit composer/drupal-default-config@8b945e80
The files are now cached in a sub-directory called lakedrops-drupal-config
of the composer cache path. The lifetime of those files is 1 day / 24 hours. If you want to manually flush that cache, you can use composer lakedrops:configuration:flush_cache
.
At the same time, default config and patches moved from gitlab.lakedrops.com/composer/plugin/drupal-environment
to this new repository at https://gitlab.lakedrops.com/composer/drupal-default-config
Note that the patch files are in the patches
directory and no longer in a d10
sub-directory of it.
Please update your Drupal project accordingly.
closed
removed Doing label
mentioned in commit drupal-environment@01d2ac85
Note that the default config and patches in the composer/drupal-default-config project won't be tagged with versions, so a change in those files doesn't immediately trigger an update on all Drupal sites.
reopened
added Documentation label
unassigned @jurgenhaas
EN: This issue hasn't been active for 3 months and will be closed in 2 weeks, if it still doesn't see any updates.
DE: Dieses Issue ist seit 3 Monaten inaktiv und wird in 2 Wochen automatisch geschlossen, falls es sich nicht ändert.
added dormant label
removed dormant label