Composer

I was pleased in starting with the composer approach to drupal installation and dependency managing. Though I'm still facing something contentious: composer is launched by a user with his shell but files are originally though as if they have to be managed by the user with no shell related to the httpd process, at least as far as disk writes are concerned - i.e. possibly file uploads... I wonder what is the best practice someone else before might have already found in order to make composer usage compatible with the usage of the drupal administration interface?

Thanks in advance!

Andrea

The directory structure of the popular drupal-composer/drupal-project uses "/web" as the Drupal project root. Clarification could be helpful for beginner/intermediate developers.

What is the current best-practice placement of everything (files/folders, etc) in a Drupal project in relation to web document root -- in a sub-folder (like the drupal-composer/drupal-project appears to use) -- or in web document root proper.

Disclaimer: I haven't been living and breathing Composer for the last few years. I took some much needed time off from Drupal to get an album out and to reestablish some balance in my life. But I'm back in it again, and discovering all the joys and sorrows of our evolving Composer support. I'm not philosophically opposed, and I'm all in favor of the Get Off The Island(tm) movement.

Hey Guys -

What do you think about a composer plugin to run Drush or Drupal console commands based on a composer operation? As I was wanting to streamline the Drupal composer workflow. I came up with a project that tried to provide a solution.

https://github.com/droath/drupal-module-installer

Would like to get suggestions about using this approach? Or other solutions that you've came up with in recent Drupal 8 projects.

About a month ago composer switched to https-only downloads.

This broke my composer-only setup, as it relied on "composer create-project drupal/drupal:8.0.5". The packagist.org package for drupal/drupal still has a http url, see https://packagist.org/packages/drupal/drupal
Locally I can fix that with the secure-http option, but it's not advised and it's also not possible on the devops platform I am using.

drupal/core looks to be ok, as it points the drupal-composer git repository.
drupal/drupal also exists on drupal-composer.org, but seems to only have the 8.0.0 (& 8.1.0) version.

... of Composer & Drush, anyway.

Composer may be the NewDrupalWay(tm), but Drush is still indispensible for much workflow. Working with both is a necessity.

So what's a Drone to do?

Here's a scenario from a (intended to be) Composer-only install. The how-to was cobbled together from the 1000-or-so blog posts, etc that keep telling us to "Get off the island" ... If anyone cares to share a/the "Definitive Current Composer HowTo for Drupal8", please pipe in!

(1) Install Drupal

Hi all,

After reading http://www.vmdoh.com//blog/building-drupal-8-website-composer I take it as Composer is a real thing within the community and the way to go to develope Drupal 8 websites to get a lot of really smooth and clever automation going.

The article also pointed me to the https://packagist.drupal-composer.org/ resource and I created an account there.

Over in the webmasters queue I have started a discussion around a PR effort to get contrib module maintainers to add composer.json files to their modules.

Please join in and spread the word.

https://www.drupal.org/node/2547385

This is a tad obscure since it's an older version, but-

GET https://packagist.drupal-composer.org/packages/drupal/admin_views.json

The link return for version 7.1.2-

http://ftp.drupal.org/files/projects/admin_views-7.x.1.2.zip

is incorrect. It should be-

http://ftp.drupal.org/files/projects/admin_views-7.x-1.2.zip

I don't expect a lot of feedback, however, I thought that I would post this here, so that it gets more visibility.

I've turned this into a blog post over here.

Literally, I wanted to convey that, if you are having problems with a specific module is required that has a package with a different name. For example in this error:

Problem 1
 - drupal/api 7.1.9 requires drupal/gplib >=7.2.1, <7.3.0 -> no matching package found.

I am submitting a session proposal on using Drush with Composer at DrupalCon LA.

Primary topics:

• The old and the new
  • drush make => composer install
  • drush dl => composer require
  • drush pm-update => composer update
• drush composer-generate
  • Drupal 7
  • Drupal 8 "split core"
  • Drupal 8 without "split core"
• site-local Drush
  • Single autoload.php for Drupal core, Drupal modules, and global Drush extensions
    vs
  • Separate autoload.php for Drush extensions

I submitted a session for the dev days about drupal and composer, but after the sessions got official, I now see that also another session were submitted.

I would like to drawback my proposed session, and maybe join up in making the other session, don know who submitted the session though...

I registered the domain http://drupal-composer.org/ and put some simple html page on that domain to direkt to different sources relevant for Drupal Composer. The source code is managed in https://github.com/drupal-composer/drupal-composer.github.io and directly hosted as Github Page.

Feel free to make changes to it by posting PRs:)

Additionally I created a first version of a Drupal Composer icon some time ago and put in https://github.com/drupal-composer/drupal-composer.github.io/tree/master... .

Posed an issue to the infrastructure queue to ask for the virtually impossible :)

https://www.drupal.org/node/2420929

The drupal-composer-project template currently resides within the Reload organisation on GitHub.

derhasi has been doing a great job keeping his fork up to date with his latest development and the fork is currently a better template for starting out new Drupal 7 projects with Composer.

How about we transfer the repository to the drupal-composer organisation and merge in derhasis changes to the composer.json file?

After weeks of back and forth the Drupal 8 core's composer.json file has now been moved to the core directory to facilitate fetching only the contents of the core directory via Composer.

The relevant issue is https://www.drupal.org/node/1975220. A big shoutout to everyone who moved that issue forward, most notably dawidwbaratt, daffie, bojanz and alexpott.

I'd like to share some thoughts on composer installers that we can use for supporting setting up a Drupal project with composer. I'd like to know about your assumptions and how we may be able to build common installer, that we can use maybe as a standard in the future.

This Wiki page should provide an up to date state of discussions and projects. So be bold and update and add resources!

Main resources

• Composer

Drupal projects

• Composer (drush plugin)
• Composer Manager
• Github organization for future releases
• Composer Generate: drush extension to generate a composer.json from an existing installation

Discussions