"Install Drupal CMS locally with DDEV” assumes unix/linux cli

Created on 12 February 2025, about 2 months ago

Problem/Motivation

The instructions on “Install Drupal CMS locally" with DDEV assume that the reader is using a UNIX/Linux machine with a bash (or similar) CLI.

I’m guessing that a significant portion of the readers of this page will be those who are new to Drupal and, therefore, are just as likely to be using a Windows machine.

The ./launch-drupal-cms.sh command won’t execute on Windows.

Steps to reproduce

Use a Windows PC to follow the instructions on the page.

Proposed resolution

Instructions should probably use the composer command via ddev. Something like...

ddev config --project-type=drupal11 --docroot=web --php-version=8.3
ddev composer install

Remaining tasks

Check the instructions on an actual Windows PC and adjust as necessary.

🐛 Bug report
Status

Active

Version

1.0

Component

Documentation

Created by

🇬🇧United Kingdom rachel_norfolk UK

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @rachel_norfolk
  • 🇳🇴Norway hansfn

    Just for the record: DDEV is pushing WSL very hard, so it's unlikely that you don't have a Bash CLI if you have DDEV - either on Linux, MacOs or on Windows via WSL.

    I suggest making it clear that we follow the "Recommended, best performance, most reliable" solution (on Windows) - using "Using WSL2 with Docker inside".

  • 🇬🇧United Kingdom rachel_norfolk UK

    They will quite possibly have a Bash CLI. Especially if they are a new user, though, it may not be clear at all that they need to use it.

  • 🇳🇴Norway hansfn

    I don't see how a new (Windows) user installing DDEV in WSL can avoid being exposed / informed about the terminal.

    Now you can use the “Ubuntu” terminal app or Windows Terminal to access your Ubuntu distro, which has DDEV and Docker working inside it

    AFAICT the "ddev" command doesn't even work in PowerShell or in Cmd if you install it inside WSL.

    In Step #1 we write "Confirm that it is installed on your machine by running the command ddev --version in the Terminal." This is the point where we might loose a Windows user if he/she has forgotten that this is the Ubuntu terminal. If you pass this point, running "./launch-drupal-cms.sh" in the terminal should not be a problem.

    For the record / slightly off-topic: I tested very quickly in my Ubuntu and I manage to make two "mistakes":

    1. I managed to unzip the zip file so launch-drupal-cms.sh wasn't executable. "./launch-drupal-cms.sh" just gave "Permission denied".

      Suggested solution: Use "bash launch-drupal-cms.sh" as command. It doesn't require executable bit and it makes it clear that bash is needed.
    2. Running the launcher gave "Apptype must be one of backdrop, cakephp, craftcms, django4, drupal, drupal6, drupal7, laravel ..." and nothing starting. (My ddev was outdated.) This will not happen to a new user of course

      Suggested solution: Add a version check in the launcher script so too old ddevs are detected.
  • 🇺🇸United States drumm NY, US

    The Drupal CMS documentation is currently canonically at https://git.drupalcode.org/project/drupal_cms/-/tree/1.x/docs?ref_type=h... and then copied over to new.drupal.org

  • 🇺🇸United States drumm NY, US

    This may already be updated for upcoming versions, see Replace the launcher script with better documentation Active

  • 🇺🇸United States thejimbirch Cape Cod, Massachusetts

    The launcher was removedand the documentation was updated in Replace the launcher script with better documentation Active . Closing as duplicate.

Production build 0.71.5 2024