2015-10-15
Tasks in web wizard (wwiz) are divided in three categories: configuration, debug, and action.
The configuration tasks role is to prepare the config values for the action tasks.
The debug tasks are utility for wwiz hackers.
The configuration category tasks are all suffixed with the asterisk symbol (*).
This is a new feature from bash manager 1.04, which allows a task to be executed no matter what.
This feature was clearly designed to create configuration tasks.
So now let's go through each task and explain briefly what it does.
possible values: 0 | 1
- 0: indicates to other tasks that passwords should be displayed in plain text in the terminal
- 1: indicates to other tasks that passwords should not be displayed in plain text in the terminal
If you are not paranoid and have no one behind your shoulders, you probably want to set this setting to 0 so that you know exactly which command is executed.
It has no consequence on the actual command being executed, it just alter the visual output.
Imagine you execute an ssh command in bash. The part between the ssh keyword and the distant command that you execute is what sshString represents.
If you use the ssh config trick, this can actually be only one word. If you don't, it can be something like:
sshString(php)*:
sketch=12.34.56.78 -p 2424 -i ~/.ssh/id_dsa_keyone -l lingtalfi
The value of this task is executed in every command that connects to the remote server via ssh.
Those are respectively the db parameters for your local machine and your remote machine. The task value is composed of three components separated by the colon symbol (:). The first component is the database name, the second component is the database user, and the third component is the database pass.
taskValue: <databaseName> <:> <databaseUser> <:> <databasePass>
This tasks's value is used whenever a patch is applied, using either the patch2Local task or the patch2Remote task.
A patch here refers to a simple file which contains sql statements.
This type of patch might be useful if you make small changes in your local database
that can be applied directly on the remote database without the need to interrupt the application.
For instance, adding a new table can be patched to your remote database without the need to interrupt the application.
The task's value represents the location of the patch on the filesystem of your local machine.
Defines the tmpFile that "database save-apply" tasks use.
This task display the keys and values of the CONFIG array. If you extend the webwizard, it could be useful for debugging purposes.
This is the first database task. From now on, the tasks use the values put in the CONFIG by configuring tasks.
This task dumps the remote database and in the file which path is specified as the task's value.
This task acts like the downloadDb: it dumps the remote database and in the file which path is specified as the task's value. However, it also applies the downloaded file (which is a bunch of sql statements) to your local database.
As we said before, a patch in this context is a file containing a bunch of sql statements. This task applies the patch (which path was given by the patchLocation task) to your local database.
This task applies the patch (which path was given by the patchLocation task) to your remote database.
This task dumps your local database (structure and data) to the file which path is given by the task's value
This task dumps your local database (structure only) to the file which path is given by the task's value
Do the basic mysql < file and mysqldump operations in any direction using two consecutive commands. Gives more power to your fingertips.
Takes no value. Dumps the local database to the tmpFile defined by the tmpFile task. Uses the basic mysqldump command.
Takes no value. Dumps the local database to the tmpFile defined by the tmpFile task. Uses the mysqldump command with the drop-database feature.
Takes no value. Applies the sql statements stored in the tmpFile defined by the tmpFile task to the local database.
Takes no value. Dumps the remote database to the tmpFile defined by the tmpFile task. Uses the basic mysqldump command.
Takes no value. Dumps the remote database to the tmpFile defined by the tmpFile task. Uses the mysqldump command with the drop-database feature.
Takes no value. Applies the sql statements stored in the tmpFile defined by the tmpFile task to the remote database.
Those tasks help doing batch tasks, like renaming all the files in a folder, or resizing all images in a folder, that kind of things.
Batch File Treatments is based on a workflow that you can adopt if you want.
First, you copy a directory to a working directory, so that your original files are left untouched. This is called import. Then, you work on the files in the working directory (resize, rename, ...) The last step is to export your work to a destination directory of your choice. This is called export.
Defines the value of the default import dir. If you don't specify the import dir location via the command line, the defaultImportDir value will be used.
Defines the value of the default export dir. If you don't specify the export dir location via the command line, the defaultExportDir value will be used.
Defines the location of the tmp dir (working directory).
Copies the content of the import directory to the working directory. As of 1.3, on mac, it also opens the working directory in the finder.
Cleans the working directory, and copies the content of the import directory to the working directory. As of 1.3, on mac, it also opens the working directory in the finder.
Resize the images (jpeg, png, gif) in the working directory. The syntax (assuming you are using ling aliases) is:
wwiz resize 600x400Where 600 is the max width and 400 the max height. The image keeps its proportion. Images are replaced inline (no copy).
Rename the files in the working directory. The syntax (assuming you are using ling aliases) is:
wwiz rename {fileName}.{ext}The allowed tags are:
- {fileName}: the file name as defined in the file name convention
- {ext}: the file extension
We can apply some functions to the tags using the ornella tag notation.
Copies the content of the working directory to the export directory.
Cleans the export directory, and copies the content of the working directory to the export directory.