- 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:
- Visit DDEV Gitpod launcher.
- Enter `https://git.drupalcode.org/project/drupal_cms` as the git repository.
- Delete the git repository with artifacts field.
- Open Gitpod.
- Replace
config.allow-plugins: true
withconfig.allow-plugins: { }
. - Run
ddev composer install
and said yes to plugin install prompts except fortbachert/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.