WP-CLI GUI: An Interface to Speed Up WordPress Installation

wp-cli-gui

WP-CLI GUI is a new tool from WordPress developer Tim Brugman, created to speed up the creation of new WordPress sites when using WP-CLI. The tool captures the details required to configure the database, site info, admin user, and password. It outputs one long command that WP-CLI users can copy and paste.

At first it might seem counterintuitive – if you use the command line to manage WordPress, why would you want to add an extra interface to your workflow? Brugman explained the problem that led him to create WP-CLI GUI:

“I heard about WP-CLI and gave it a shot,” he said. “I thought it was very neat for managing your sites but a bit of a hassle for new installs. Because installing WP with the CLI is a sequence of commands, if you don’t concatenate them, you have wait for each to end. It’s especially annoying because the first, downloading WP, takes the longest.”

If you concatenate all of the commands into one giant command with all of the installation variables, the risk of typos increases to where you need to copy and paste.

“Once I started copy pasting, I figured I might as well automate that with JavaScript,” Brugman said. “That became the ridiculous GUI for the CLI.”

Brugman plans to expand with options for removing Akismet and Hello Dolly and is considering adding a list of optional plugins to install.

“Depending on the number of plugins you ‘always’ use, could save some more time,” he said. “Tasks beyond the installation I haven’t yet looked at. Requests are welcome.”

WP-CLI GUI is supported by Toscani, a web development company. Brugman and his colleagues there use the tool to speed up installation of new WordPress sites. He said the tool is ideally suited for developers who often create new WordPress sites and are comfortable with the command line but don’t use WP-CLI at every opportunity.

8 Comments


  1. > options for removing Akismet and Hello Dolly

    No! Next time they will also remove the sample post, sample comment and sample page!!! We must stand united against those changes. WordPress must keep those things forever!!! Howdy, Dolly!

    </joke>

    Report


    1. On a serious note, I believe the whole concept of WP installation should somehow turn towards a single place for WP per server and not WP-per-site (not talking about multisites with their “quirks”).

      I am using Composer and install WP always in a folder, where it stays separately from the application (WP_CONTENT points to the “app” folder). Then, why can’t I have the “wp” folder somewhere in /usr/local/wordpress-{version} and just use it from there?

      </a thought>

      Report


      1. Well .. if you got servers to waste .. do it.
        Not a realistic scenario for shared hosting though.

        ie. yet another one of those .. *groans*

        cu, w0lf.

        Report


  2. I just use the –prompt flag on most of these commands and WP-CLI asks you for everything it needs.

    Report


  3. Cool stuff Tim! I’ve just written out all of the install command lines into one big text expander snippet. It helps that I’m usually deleting the install once I’m done and reinstalling so I don’t have to worry about new passwords, etc. Your GUI is cool for that though!

    Report


  4. WP-CLI GUI ? Isn’t that just WordPress?

    Surely if you want to install WordPress and want to copy & paste the values without having to use the command line, you could just use wp-admin/install.php ?

    Report


    1. Yeah, that was my thought, too. 1st of April is already over for this year.

      GUI for a CLI for a GUI? Whats next, Node.JS in JVM?!?
      (oh wait, they already commited THAT crime o.O)

      cu, w0lf.

      Report

Comments are closed.