[3558437] DrupalPod-AI-QA Basic setup with starterkits
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3561522. --> Reported by: [littlepixiez](https://www.drupal.org/user/2568718) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>In Progress<br> <strong>Check-in Date: </strong>TBC<br> <strong>Additional Collaborators: </strong><br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Child issue of: <a href="https://www.drupal.org/project/ai_initiative/issues/3558437">https://www.drupal.org/project/ai_initiative/issues/3558437</a><br> Development: <a href="https://github.com/drupalforge/drupalpod-ai-qa/tree/main">https://github.com/drupalforge/drupalpod-ai-qa/tree/main</a></p> <p>QA testers need to be able to spin up a DrupalPod QA image quickly without complex local setup. The first step is being able to choose between Drupal CMS and Drupal core as a starting point, and choose a version and this be working.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>- Starterkit selection works (CMS or core)<br> - Version selection works (DP_VERSION)<br> - Site spins up and is functional<br> - User can log in with admin/admin</p> <p><strong>Acceptance criteria</strong><br> - I can set DP_STARTER_TEMPLATE=cms and get a working Drupal CMS site<br> - I can set DP_STARTER_TEMPLATE=core and get a working Drupal core site<br> - I can change DP_VERSION and it pulls the correct version<br> - I can log into the admin interface with username: admin password: admin</p> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <p>TBD</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>- Confirm final working version of ddev<br> - Get this working with Drupalpod<br> - Development<br> - Testing<br> - Documentation</p> > Related issue: [Issue #3558437](https://www.drupal.org/node/3558437)
issue