At the moment there are two ways to keep the list of modules up-to-date:

  • By importing the whole XML from updates.drupal.org/release-history/project-list/all
  • By entering the shortname directly (this will trigger an initial fetch of the project data by parsing the project page)

There should be found a better way without manual maintenance.

Proposed solutions:

  • Parsing the "new modules" RSS feed

Comments

Deciphered’s picture

Could add a Cron based version of the Automatic download method of the Simplytest import process, and tie it to the QueueAPI for processing the data.

One thing to take into account is that as the QueueAPI based batching approach can take considerably longer as it's generally tied to Cron, you wouldn't want to flush the projects each time it's initialised.

You could speed the process up by running the Drush queue daemon as well.

patrickd’s picture

hmm,

maybe adding a chronjob which executes a script like:

wget http://updates.drupal...... -O /tmp/projects
drush simplytest-import /tmp/projects

Adding "simplytest-import" as drush command for incremental import (that should be fairly easy as new projects only get added to the XML's bottom AFAIK)

Deciphered’s picture

As much as I like the idea of having a Drush command for the import, given that you still need to implement both a cronjob as well as a batching/queuing process, it seems to me that using hook_cron to invoke the initialisation of the download and queue makes more sense, as the queue will be iterated through as cron is continually invoked, or if the queue daemon is running then as soon as the queue is created it will be run through.

patrickd’s picture

Issue summary: View changes
Status: Active » Closed (outdated)