Skip to content

Latest commit

 

History

History
89 lines (60 loc) · 3.76 KB

README.markdown

File metadata and controls

89 lines (60 loc) · 3.76 KB
Raw

WordPress Plugin Directory Slurper

A command line PHP script that downloads and updates a copy of the latest stable version of every plugin in the WordPress.org plugin repository.

Really handy for doing local searches across all WordPress plugins.

Based on Mark Jaquith's project and Rarst's fork

Requirements

  • PHP 5.2
  • Curl
  • pthreads

How does this differ from Mark's and/or Rarst's version?

Mark to Rarst:

  • Changed from wget to curl so it can be used on any platform (not just Unix based ones)

Rarst to Mine:

  • Added pthread to thread the download and processing (dramatically improved performance).
  • Used curl's curl_multi_exec to allow for multiple parallel downloads (dramatically improves performance)

Unlike Mark's and Rarst's versions, which need to be left overnight to finish, this version can finish in about 30 - 60 minutes for code checkouts and 15 - 30 minutes for readme checkouts. It's much faster than any other version or fork, including the parallel wget requests one. That fork is 12x faster than Mark's version. This one is 2x the speed of that one, or roughly 24x the speed of Mark's.

Instructions

If you don't already have it, you need to install and activate the PHP pthreads extension.

  1. cd WordPress-Plugin-Directory-Slurper
  2. php update.php

The plugins/ directory will contain all the plugins, when the script is done if you asked for all. The readmes/ directory will contain all the readmes, when the script is done if you asked for readmes.

FAQ

Why download the zip files? Why not use SVN?

An SVN checkout of the entire repository is a BEAST of a thing. You don't want it, trust me. Updates and cleanups can take hours or even days to complete.

Why not just do an SVN export of each plugin's trunk?

There is no guarantee that the plugin's trunk is the latest stable version. The repository supports doing development in trunk, and designating a branch or tag as the stable version. Using the zip file gets around this, as it figures it all out and gives you the latest stable version

How long will it take?

Your first update will take much longer than any other (about 30 - 60 minutes for code checkouts and 15 - 30 minutes for readme checkouts)

But subsequent updates are smart. The script tracks the SVN revision number of your latest update and then asks the Plugins Trac install for a list of plugins that have changed since. Only those changed plugins are updated after the initial sync.

How much disk space do I need?

As of late 2013, it takes up about 12GB.

Something went wrong, how do I do a partial update?

The last successful update revision number is stored in plugins/.last-revision. You can just overwrite that and the next update will start after that revision.

Copyright & License

Copyright (C) 2015 Chris Christoff

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.