(via AI) Drupal Forge Contribution Demo Session
Drupal Forge: Cloud Development Platform
Michael and Darren discussed Drupal Forge, a platform that allows users to quickly launch Drupal CMS in the cloud. They explained that Drupal Forge is working to fill the gap left by Gitpod, which is currently unstable. Darren mentioned that he modified a Drupal Pod extension to send data to Drupal Forge, enabling remote development environments to be spun up. They also highlighted the role of DevPanel, which is sponsoring the free demos on Drupal Forge and providing the software to spin up demo sites.
Markdown Easy Plugin Architecture Update
Michael and Darren discussed the progress and upcoming steps for a merge request on the Markdown Easy module, which is nearly ready to be merged. The module will be transformed into a plugin architecture, a significant improvement that removes friction for potential contributors by allowing them to work in a pre-configured Drupal Forge environment rather than dealing with DDEV setup and issue forks. Darren noted that Vinay from Drupal Campune had improved the user interface for the extension, which makes it easier to use.
Drupal Forge Development Environment Setup
Michael and Darren discussed the setup and usage of Drupal Forge for development environments. They reviewed the process of selecting branches, profiles, and Drupal core versions, noting that choosing "none" requires manual installation. Darren explained that Drupal Forge uses containers to spin up environments, install Drupal, and manage code repositories. They also touched on the 6-hour default runtime of environments and the ability to extend or pause them. Additionally, they briefly explored the process of obtaining a token from Drupal.org to push changes to the platform, with Darren suggesting consulting the Drupal Pod documentation for more details.
Drupal Forge Issue Fork Setup
Michael and Darren discussed the setup and usage of Drupal Forge, focusing on the process of working on issue forks. They clarified steps such as using a personal access token instead of a Drupal.org password, enabling modules automatically when working on issue forks, and navigating the project route. Darren confirmed that Composer handles SIM-linking repositories correctly. Michael expressed a desire to run PHPUnit directly from the project route, and Darren confirmed this functionality.
Drupal PHPUnit Setup on Forge
Michael demonstrated how to set up PHPUnit testing on Drupal Forge, explaining the process of creating a phpunit.xml file and configuring it for the project root. He noted that SQLite is not yet supported on Drupal Forge, but provided a workaround using the default settings.php file to run tests. Michael emphasized the importance of having PHPUnit configuration for contribution purposes, and expressed hope that auto-generated PHPUnit files would be implemented in the future.
Git Workflow and Access Tokens
Michael demonstrated the process of making a minor text change to the README file while tests are running, configuring Git, committing the change, and pushing it to the Drupal Forge repository using a personal access token. He emphasized the importance of being explicit with commands and explained the steps involved in creating and using an access token for repository access.
Drupal Forge PHP Unit Testing
Michael and Darren discussed the process of running PHP unit tests on Drupal Forge, including how to pause and unpause environments, and the importance of bookmarking the staging URL for future use. They also talked about the need to regenerate the phpunit.xml file due to potential changes in environment variables when the app is unpaced. Darren mentioned that DevPanel, the platform used for Drupal Forge, is also useful for enterprises managing their own hosting. They agreed to collaborate further on generating the phpunit.xml file, with Michael offering to share his working environment with Darren.
Add new comment