Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Allow starting a new Panopoly project from scratch via Composer:
composer create-project panopoly/panopoly-composer-template:8.x-dev somedir --no-interaction
TODO
- #3051081: Allow composer to pull in the CKEditor plugins we need
- Document (both in the project README, but also on the D.o project)
Original summary
is there some composer command for installing panopoly like there is for so many other projects in drupal ecosystem eg composer create-project acquia/lightning-project:^8.1.0 MYPROJECT --no-interaction .... this would be so helpful. many thanks for this great distro. cheers
Comments
Comment #2
remyyyyyHeLLo @drupalstrap,
This is not an ideal answer but you can install Panopoly with drush :
drush dl panopoly --select
drush si panopoly --db-url=mysql://[db_user]:[db_pass]@[ip-address]/[db_name]
Cheers
Comment #3
dsnopekNot right now, but this would be super awesome! Patches welcome :-)
Comment #4
dobie_gillis CreditAttribution: dobie_gillis commentedUpdating/installing with drush no longer works, see: https://www.drupal.org/project/panopoly/issues/2940744
At the very least, we should add instructions on how to install an older version of drush that allows this to work, if composer isn't supported.
Comment #5
dsnopekUpdating title. I'm going to start working on this soon
Comment #6
dsnopekI started this here:
https://gitlab.com/panopoly/panopoly-composer-template
However, I've been breaking my brain trying to get the dependencies of the Panopoly profile to get pulled in. For some reason, Composer only sees a dependency on 'drupal/core' but not the dependencies of the profile (ex. panopoly_core, etc). I tried putting the Git repo directly as a repository, and various caching clearing, and minor tweaks to the composer.json and it's still not working... :-/
Comment #7
dsnopekHere's a D.o issue going over my problems with Panopoly (and very similar problems with civicrm_entity that I had some months ago):
#3051746: Composer facade seems to be auto-generating info when a composer.json is present
Comment #8
dsnopekThe weird composer facade issue still seems to exist, but I found a workaround. The next step is solving #3051081: Allow composer to pull in the CKEditor plugins we need so that the WYSIWYG editor works!
Comment #9
dsnopekAdd a TODO to the issue summary
Comment #10
dsnopekComment #11
dsnopekI just closed #3051081: Allow composer to pull in the CKEditor plugins we need.
I kept having issues with the Drupal.org Composer Facade, so ended up switching to a solution like Lightning uses, where the profile is actually a Packagist package hosted off of Drupal.org. Here's the mirror repo:
https://gitlab.com/panopoly/panopoly
The package is 'panopoly/panopoly' rather than 'drupal/panopoly'. This isn't ideal, but the issue was hitting was where sometimes 'composer update' would see my workaround, and sometimes it wouldn't, and non-deterministic behavior is worse than a non-standard package name.
However, this does mean that at some time in the future, if Drupal.org starts worknig better, we may need to deprecate 'panopoly/panopoly' in favor of 'drupal/panopoly'
What remains here is documentations! We need a better README on the panopoly-composer-template, and we need to get this in as the installation instructions for Drupal 8 in all the key places.
Comment #12
dsnopekTested and documented! I'm gonna count this one as fixed - anything else should go in a new issue