Replace the launcher script with better documentation

Needs sign-off from @pameeela and @tim.plunkett.

I propose we fully remove the launcher from Drupal CMS 1.1.0, and in the next 1.0.x release, we keep the launcher there but update the README.md file.

I agree that “less is more” and we shouldn’t maintain stuff that’s not adding enough value. Those of us that use DDEV or the command line are comfortable with a few extra commands. Those who aren’t comfortable with the command line probably won’t be testing it this way anyway.

I think this is technically impossible to update for sites because it's in the composer template. And while we would not expect people to ever run it more than once, more or less immediately after downloading, not having code sitting around that can never be updated is good.

That's a great point, and certainly another nail in the launcher's coffin.

Sold.

Just needs final sign-off from @pameeela.

Tweaked the wording to try to make it super clear that DDEV is just one option. It's not *recommended* per se, it is just the one we are supporting.

But otherwise looks good to me!

Once this lands, this page needs updating:

https://new.drupal.org/docs/drupal-cms/get-started/install-drupal-cms/in...

@kristen pol: Only when we release 1.1.0. That's why we're keeping the script in the 1.0.x branch, although updating the README in both branches.

I guess I would have removed the zipball entirely and just done the `ddev composer create`. What's the value of the zipball here?

@eojthebrave or I will take care of updating the documentation in the Drupal CMS User Guide at the appropriate time. We'll check in with @pameeela about when it should be updated.

@amber himes matz: It should be updated when we release Drupal CMS 1.1.0, since that's the first version that will not have the launcher. :)

@rfay: We can't really "remove" the zipball because it's needed when we're generating release nodes on drupal.org.

Well, you don't have to *use* the zipball :) Or tell anybody it exists!

That would be one to bring to the DA, I think; the download link on https://new.drupal.org/download is not under my control. :)

You don't even need ddev config --project-type=drupal11 --docroot=web because ddev config --project-type=drupal --docroot=web will work as ddev recently changed the drupal alias from drupal10 to drupal11. We are assuming some ddev defaults here that ddev might change. I don't know what oversight or warning we might get of those.

I think --create-docroot is also now a default and I don't think it was before.

Related to https://www.drupal.org/project/drupal_cms/issues/3500075 📌 Test (and then possibly document) installing on shared hosting Active , but what about PHP version? A shared hosting provider might only offer PHP8.3 and Drupal Core 11.1 supports PHP8.4. What happens when PHP8.3 is no longer supported (by Drupal or PHP).

No action required, just a reminder that what works now might easily change. I'm not suggesting we re-enable that installation script, but a more intelligent installation script might be exactly what we need in the future to help more people install Drupal CMS more easily.

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

This is a breaking change in a minor release and therefore definitely needs a change record. We also need to update the documentation pages on drupal.org that refer to the launcher script, which is a release-blocking task.

Created the change record, it just needs details filled in. https://git.drupalcode.org/project/drupal_cms/-/wikis/Committer-Info/Cha... can be used as a template.

Finished the change record.

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