In a shared CentOS with Bash I ran under ~/public_html/example.com:

composer require drupal/drupal

The output was one dir and two files:


That's not what I expected... I Expected to have a Drupal zip/tar downloaded, extracted and then deleted, and the directory filled with Drupal content.

The Drupal content I'd hope for is a common, stable/LTS (8.5.x) and non-minimal, "trivial" install.

How could I achieve just that?


I'd prefer not to use Composer because I'm not a PHP developer and I don't want to learn Composer.

Given this cannot be done with Drush, maybe it is possible some other way with Drupal Console?

I cannot use shell globs in this shared server environment so customizing something with wget or curl isn't possible.


Strictly speaking, you can implement whatever workflow makes sense for your own requirements - there aren't really any limits imposed by Drupal itself. But a lot of people (maybe most?) use the Composer Drupal project.

That makes an installation as easy as:

composer create-project drupal-composer/drupal-project:8.x-dev some-dir --stability dev --no-interaction

That project also includes Drupal scaffold, which as part of the Composer-based install/update process, will help to keep the non-package files (e.g. .htaccess, development.services.yml, etc.) up to date automatically.

  • Thanks. I don't want to use dev stability. I'd like a regular install, just as I would have if I manually download and install Drupal 8.5.x in a trivial way. I've edited the question to clarify that. I can only hope you'd agree to edit the answer to remove the dev stability. – JohnDoea Aug 30 '18 at 11:58
  • @JohnDoea – Just run that command. And then edit your composer.json afterwards. drupal-composer/drupal-project will probably always be dev. But this is just a wrapper. – leymannx Aug 30 '18 at 12:01
  • 1
    @JohnDoea That's the recommended, possibly only, way to use the installer for the Drupal project, so I'll leave it as-is (it'll be confusing otherwise). That's exactly the point I was making in the first paragraph, though. If you don't want dev stability, and you can fashion a workflow that gets what you need without it, then that's exactly what you should do – Clive Aug 30 '18 at 12:08
  • 1
    Just to address your update: Drupal all but requires Composer now, there's no point fighting it if you want to use Drupal >=8. All you're doing is making extra work for yourself, and it'll become increasingly difficult to update your sites over time as Drupal becomes more and more dependant on Composer – Clive Aug 30 '18 at 12:13

Not the answer you're looking for? Browse other questions tagged or ask your own question.