Status? Working? Roadmap? Help?
@totten That is a very interesting development, being able to do a full CMS + CiviCRM + extensions install reliably via composer is very appealing. What is the status of this development? Any bits already working? What would remain to be done for a first (limited) release?
A few comments:
- as rightly stated in the README, having an existing composer repo to draw from will get people interested. We can leave the choice of 'where to run composer?' to the end-user and not worry about it for now.
- there already is a 'civicrm-ext' location defined in the composer library installers. Is it compatible with a stock civicrm install (ie. not requiring further configuration), and would it support this use case?
- long-term we should probably split: - info.xml: general information on the extension, to be consumed primarily by end-user through the extension directories (c.o, in-app) - composer.json: technical dependencies information, to be consumed by code management tools & runtimes