The library civicrm-setup is largely a a reorganization of the older civicrm-core/install folder, which is the web-based installer used on Drupal/WordPress/Backdrop. However, the Joomla integration always had a separate installer.
A good next-step for supporting Joomla would be introducing CLI support. Some activities involved:
There will be an extra requirement (that's not part of the WordPress.civi-setup.php example): during the civi.setup.installFiles event, you need to create an extra copy of civicrm.settings.php which is slightly different. (One copy for backend/admin; one copy for frontend/user.)
When we have installer logic that works on Joomla CLI, then it should be easier to update Joomla web UI to also use civicrm-setup.
The library
civicrm-setupis largely a a reorganization of the oldercivicrm-core/installfolder, which is the web-based installer used on Drupal/WordPress/Backdrop. However, the Joomla integration always had a separate installer.A good next-step for supporting Joomla would be introducing CLI support. Some activities involved:
Joomla.civi-setup.phpplugin. Perhaps use WordPress.civi-setup.php as an example.WordPress.civi-setup.phpexample): during thecivi.setup.installFilesevent, you need to create an extra copy ofcivicrm.settings.phpwhich is slightly different. (One copy for backend/admin; one copy for frontend/user.)When we have installer logic that works on Joomla CLI, then it should be easier to update Joomla web UI to also use
civicrm-setup.