Created on 10 January 2023, over 1 year ago
Updated 12 October 2023, 12 months ago

Documentation location/URL

https://www.drupal.org/docs/official_docs/en/_evaluator_guide.html β†’

Problem/Motivation

Was not able to get Drupal running on local Mac by following the current steps.
When following the current steps, ran into several errors when trying out demo_umami on local Mac running Ventura 13.1.
PHP is no longer included since MacOS 12.

Proposed resolution

May need to add an additional step in here about using HomeBrew to install PHP.
If installing the latest, per the instructions, you will end up with Drupal 10, which has a PHP requirement of 8.1 β†’ .

To make it simpler, would recommend quick-start standard instead of demo_umami. With Drupal 10s default Olivero on the front and Claro on the back, it's a great experience out of the box.

Remaining tasks

Update instructions
Suggested revisions
https://www.drupal.org/files/issues/2023-01-10/guide_evaluator.asciidoc β†’

πŸ“Œ Task
Status

Fixed

Version

9.0

Component

Content

Created by

πŸ‡ΊπŸ‡ΈUnited States rovo Delaware

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡΄Norway hansfn

    The PHP 8.1.6 requirement has been added earlier. I just added a sentence about what to do if PHP is missing.

    I agree that maybe the standard profile is a better demo, simpler, but I think that decision should be done in a separate issue - if you still care.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Thanks for reporting this @rovo. We could include a link to this page: https://formulae.brew.sh/formula/php

    Maybe you can check if that would fix the challenge for MacOS users, and the quick-start command works after that?

    I do think Umami profile is best used here as a showcase, demoing what Drupal is capable of with multilingual, search, default content, etc.

  • πŸ‡³πŸ‡΄Norway hansfn

    I added the link to the PHP installation manual (which contains MacOS specific instructions - that uses Homebrew) to avoid adding links to solutions for specific operating systems. If we start doing that, this is no longer a quick / short guide.

  • πŸ‡³πŸ‡΄Norway hansfn

    I see that you have added instructions for MacOS and one family of Linux. What about all the other Linux distros that don't use Apt? What about Windows? I hope we can agree on just point to the PHP manual which has sections for each OS. (If that manual isn't good enough we should work to improve that. At least in a perfect world.)

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    I did it like that because ~80% of users in the "2023 Drupal Local Development Survey" use MacOS or Debian-based Linux. If we want to guide MacOS users to Homebrew anyway, I think we should link there directly, since that is much quicker.

    ... nearly 56% of users on Macs [...] Debian-based Linux is overwhelmingly the most popular Linux distro family. (24%)

    From https://www.ironstar.io/devsurvey23/#operating-system-usage

    It's a good point about Windows and other Linux distros, I have added a note about that, with the link to PHP page.

  • πŸ‡³πŸ‡΄Norway hansfn

    I object :-) He-he. I'm not going to argue further, but I'm going to repeat my standard point of view: In the Drupal documentation, we should focus on documenting Drupal specifics. (I'll not list the pros - and cons - of this approach now.)

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Thanks for letting this one slip and (pragmatically) allow new users to try Drupal much faster :-)
    But I do agree that we shouldn't get too OS specific, as a rule of thumb.

  • πŸ‡ΊπŸ‡ΈUnited States rovo Delaware

    Thanks @ressa and @hansfn for all your efforts. This page reads better, especially with the CODE blocks.

    An aside, I wonder why the URL page name has a leading underscore.
    https://www.drupal.org/docs/official_docs/en/ β†’ _evaluator_guide.html

  • πŸ‡³πŸ‡΄Norway hansfn

    These pages was treated specially earlier so I assume the underscore tried to tell that. We could remove it now :-)

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024