[policy] Adopt an officially supported cloud-based IDE/dev environment

Created on 25 September 2024, 9 months ago

Problem/Motivation

This is a policy-only issue, so it should not have a merge request.

When someone starts a project with Drupal CMS, they need to be able to see it and work on it before it gets deployed. Right now, we have support for DDEV, which is a Docker-based runtime. I'd like us to also add support for a local, non-Docker runtime (see πŸ“Œ [policy] Adopt an officially supported non-Docker runtime Active for that discussion). Additionally, I think we should support people who are either unable or unwilling to install any local runtime -- in other words, we should choose some cloud-based dev environment, like GitPod or StackBlitz or some other alternative -- and officially support it in our documentation and project template.

So let's talk about it. Any preferences here? Is this a good idea at all?

πŸ“Œ Task
Status

Active

Component

Infrastructure

Created by

πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

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

Comments & Activities

  • Issue created by @phenaproxima
  • πŸ‡ΊπŸ‡ΈUnited States jcandan

    After reading https://git.drupalcode.org/project/drupal_cms/-/wikis/Contributing-to-Drupal-CMS and finding out that the trial experience is built on DDEV, I attempted to fire up Drupal CMS via DDEV Gitpod launcher.

    It works. However, it does not support Project Browser out of the box, but not in the same way as πŸ› Fix Project Browser returns 0 results in Trial Experience Active . I get composer errors. I trudged through a couple, but hit a wall.

    Not extensively tested other than that.

    Steps followed:

    1. Visit DDEV Gitpod launcher.
    2. Enter `https://git.drupalcode.org/project/drupal_cms` as the git repository.
    3. Delete the git repository with artifacts field.
    4. Open Gitpod.
    5. Replace config.allow-plugins: true with config.allow-plugins: { }.
    6. Run ddev composer install and said yes to plugin install prompts except for tbachert/spi.
  • πŸ‡ΊπŸ‡ΈUnited States jcandan

    Go forward with an issue to get that Gitpod launcher working?

  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    Thanks for trying it, and reporting back! I'd say hold off on making an issue for now; it has not yet been decided that this is worth pursuing. The trial experience is absolutely not meant to be used in GitPod or anything else - it's strictly intended to be executed in a Wasm runtime, at least for the time being. This is more about getting "real" Drupal CMS projects to work, and there's no officially sanctioned way (yet) to start those.

  • πŸ‡ΊπŸ‡ΈUnited States darren oh Lakeland, Florida

    We have had people from the Drupal community working on this ever since the Starshot initiative was announced. More discussion has to happen for this to become an official part of Drupal CMS, but anyone who wants to work on it now can join the Drupal Forge project β†’ . You can see our progress at drupalforge.org. Try both the Drupal 11 and the Drupal CMS launch buttons to get an idea of what it can do. Join the #drupalforge channel on Drupal Slack to learn more.

  • Status changed to Closed: won't fix 5 days ago
  • πŸ‡¦πŸ‡ΊAustralia pameeela

    Discussed with @phenaproxima that we aren't pursuing this in light of the launcher app. Happy for solutions like Drupal Forge and Gitpod to continue but no plans to choose an 'official' environment right now.

Production build 0.71.5 2024