Installing and testing
Since WordShell is a shell script, you can run it in two ways:
1) Invoke it by calling bash, as follows:
bash wordshell --version
2) Place it in one of your binary directories (e.g. /usr/local/sbin) and invoke it directly, like so:
For the latter method, don’t forget to make wordshell executable (chmod +x wordshell).
You should receive an output something like so:
You can now test to see if you have all the requirements needed for running WordShell installed, by running this command:
This will hopefully produce an output like this:
All is well - you can run WordShell with 100% of available features
To get a more detailed output, add –debug:
wordshell --checkrequirements --debug
This should produce an output something like this:
Working diff was found Working patch was found Working php was found Working vi was found Working lftp was found Working curl was found Working wget was found Working rsync was found Working unzip was found Working zip was found Working w3m was found Working elinks was found Working lynx was found All is well - you can run WordShell with 100% of available features
If you have any tools missing that are essential (which WordShell will inform you of), then you should install them. Note that not all of the above tools are essential:
- curl and wget are only needed if lftp was not found; otherwise they are unnecessary.
- One of lftp or curl is absolutely required to work on any remote FTP / SFTP / FTPS sites. If all your sites are on your local filesystem, then wget will suffice. (Curl is installed by default on Mac OS X).
- rsync is not required, but if installed gives more efficient operation with any WordPress sites on your local filesystem.
- One of w3m, elinks and lynx is used to display changelogs; you only need one of them to do that, and otherwise do not need any.
Once you have installed, you are ready for your first run.
Chapter index: Starting to use WordShell