CiviCRM Composer-Extension Bridge issueshttps://lab.civicrm.org/infra/comex/-/issues2020-07-01T19:03:22Zhttps://lab.civicrm.org/infra/comex/-/issues/2Status? Working? Roadmap? Help?2020-07-01T19:03:22ZcivideskStatus? 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...@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:
1. 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.
2. 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?
3. 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 & runtimeshttps://lab.civicrm.org/infra/comex/-/issues/1The Monkey Wrench (Alternate Path for /vendor?)2019-07-19T10:57:39Zginkgomzdginkgomzd@fastmail.comThe Monkey Wrench (Alternate Path for /vendor?)I saw the discussion in the docs about where to run composer.
The only option that makes sense to me right now is for all of the installed extensions on the system to exist as dependencies of an uber project that is fully managed automa...I saw the discussion in the docs about where to run composer.
The only option that makes sense to me right now is for all of the installed extensions on the system to exist as dependencies of an uber project that is fully managed automatically by CiviCRM.
Would be great if we didn't have to fork the composer dependency resolver obviously.
I haven't done the first thing of seeing if it's possible to specify a alternate directory to "/vendor".
Is it as easy as that?