Skip to content

Composer addons with override#2432

Open
Daniel-KM wants to merge 10 commits intoomeka:developfrom
Daniel-KM:feat/composer_addons
Open

Composer addons with override#2432
Daniel-KM wants to merge 10 commits intoomeka:developfrom
Daniel-KM:feat/composer_addons

Conversation

@Daniel-KM
Copy link
Contributor

@Daniel-KM Daniel-KM commented Feb 9, 2026

Hi,

This is an history rebuild for #2412 , so it adds only the main feature and then additionnal but useful features in order to manage omeka modules and themes via the composer of omeka in directory composer-addons/, and to let people to continue to use the directories modules/ and themes/ as they used to. It is very useful to manage containers with volumes and to let freedom to users. It is fully compatible with 4.2 (except the change of the directory by the internal installer plugin, that was never used except by the default theme). So you can merge all or cherry-pick the features you want.

  • manage directory composer-addons/ with composer
  • manage priority for modules/ and themes/
  • use composer.json when available for simple and fast init
  • manage automatic inflection of installer name to simplify upgrade
  • a script to install modules dependencies for manually installed modules via git inside modules/, since composer does not inherit them (can be a composer command).

So the remaining point to think about is to use, or not, composer-merge-plugin (so two separate composer.json, a little slower).

@Daniel-KM Daniel-KM force-pushed the feat/composer_addons branch from e005f33 to 152534f Compare February 9, 2026 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant