>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1243332. --> >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The Project Browser module enables users to search for and install modules and themes from within their Drupal site's admin area, instead of having to go to drupal.org and copy/paste the download link each time. This is a huge UX improvement. Targeting to be included in D8 Core.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>To get the Project Browser module working, we need to deploy the following two modules on Drupal.org:</p> <p>project_browser_server<br> ----------------------<br> This module provides an API as well as endpoints so that you can serve search results to the Module / Theme Browser module.</p> <p>drupalorg_pbs<br> -------------<br> This is an implementation of the Project Browser Server API specifically for Drupal.org, which takes advantage of the Apache Solr framework to serve results to queries. Think of it as the same thing as doing a search on Drupal.org, with all the caching and performance that provides.</p> <h3 id="summary-remaining-tasks">Remaining tasks (in order of importance)</h3> <ol> <li><del>Getting Apache Solr 6.x-3.x with a decent sized projects index working on the Dev Environments so that coding/testing can resume. Waiting for the Infrastructure team.</del></li> <li><del>Porting Project Browser Server and drupalorg_pbs to Drupal 7</del> (This still needs testing and further work once the Dev Environments are updated to use Drupal 7 and Solr)</li> <li><del>Some documentation pages could be written describing how to implement the server hooks.</del> Done - See <a href="http://drupal.org/node/1612058">http://drupal.org/node/1612058</a></li> <li><del>Thorough code review and security audit of Project Browser Server.</del></li> <li><del>Thorough performance assessment of Project Browser Server.</del></li> <li>Deploy to Drupal.org</li> </ol> <h3 id="summary-ui-changes">User interface changes</h3> <p>N/A</p> <h3 id="summary-api-changes">API changes</h3> <p>N/A</p> <h3 id="summary-original-report">Original report by wildkatana</h3> <p>I need to get Project Browser Server and drupalorg_pbs deployed on d.o for the Google Summer of Code 2011 Project Browser module. This has been tested for months on a Sandbox site, and there haven't been any issues. Development on these two modules has been completed for over a month without any changes.</p> <p>These two modules will allow Project Browser to pull project information from the live drupal.org site so that users of Drupal can easily browse and install new modules and themes straight from their Drupal sites.</p> <p>Deployment Checklist:<br> ---------------------</p> <p>1. Install and Enable Project Browser Server 6.x-1.1 (<a href="http://drupal.org/project/project_browser_server">http://drupal.org/project/project_browser_server</a>)<br> -<a href="http://drupal.org/node/1842230">http://drupal.org/node/1842230</a> (6.x-1.1)<br> 2. Install and Enable drupalorg_pbs 6.x-2.0 (<a href="http://drupal.org/project/drupalorg_pbs">http://drupal.org/project/drupalorg_pbs</a>)<br> -<a href="http://drupal.org/node/1842228">http://drupal.org/node/1842228</a> (6.x-2.0)<br> 3. In Permissions, enable 'access project browser server' for anonymous and optionally authenticated users</p> <p>Risks<br> ------</p> <p>-Performance: There will be a lot of new traffic from the Project Browser module, fetching project data. This will only take place when admins are setting up their sites and/or installing new modules and themes, and it uses the existing update.module functionality where available, so I don't foresee a big issue here. In addition, the endpoints use GET parameters and are cache-able.<br> -I don't know of any impacts, performance or otherwise, on any other subsystems.</p> <p>The project page on Drupal Groups: <a href="http://groups.drupal.org/node/145159">http://groups.drupal.org/node/145159</a></p> > Related issue: [Issue #2940733](https://www.drupal.org/node/2940733)