Ignore:
Timestamp:
03/14/14 12:36:58 (11 years ago)
Author:
hendrikvanantwerpen
Message:

Enable deployment with Grunt.

Location:
Dev/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • Dev/trunk

    • Property svn:ignore

      •  

        old new  
        11build
        2 quod-erat.git

  • Dev/trunk/node_modules/grunt-exec/README.md

    r484 r516  
    2323-----
    2424
    25 This plugin is a [multi task][types_of_tasks], meaning that grunt will automatically iterate over all exec targets if a target is not specified.
     25This plugin is a [multi task][types_of_tasks], meaning that grunt will
     26automatically iterate over all exec targets if a target is not specified.
    2627
    27 If the exit code generated by the specified shell command is greater than 0, grunt-exec will assume an error has occurred and will abort grunt immediately.
     28If the exit code generated by the specified shell command is greater than 0,
     29grunt-exec will assume an error has occurred and will abort grunt immediately.
    2830
    29 [types_of_tasks]: https://github.com/gruntjs/grunt/blob/master/docs/types_of_tasks.md#multi-tasks
     31[types_of_tasks]: http://gruntjs.com/configuring-tasks#task-configuration-and-targets
    3032
    3133### Properties
    3234
    33 *   __command__: The shell command to be executed. Must be a string or a function that returns a string. (alias: __cmd__)
    34 *   __stdout__: If `true`, stdout will be printed. Defaults to `true`.
    35 *   __stderr__: If `true`, stderr will be printed. Defaults to `true`.
    36 *   __cwd__: Current working directory of the shell command. Defaults to the directory containing your Gruntfile.
    37 *   __exitCode__: The expected exit code, task will fail if the actual exit code doesn't match. Defaults to `0`.
    38 *   __callback__: The callback function passed `child_process.exec`. Defaults to a noop.
     35*  __command__ (alias: __cmd__): The shell command to be executed. Must be a
     36  string or a function that returns a string.
     37*  __stdout__: If `true`, stdout will be printed. Defaults to `true`.
     38*  __stderr__: If `true`, stderr will be printed. Defaults to `true`.
     39*  __cwd__: Current working directory of the shell command. Defaults to the
     40  directory containing your Gruntfile.
     41*  __exitCode__ (alias: __exitCodes__): The expected exit code(s), task will
     42  fail if the actual exit code doesn't match. Defaults to `0`. Can be an array
     43  for multiple allowed exit codes.
     44*  __callback__: The callback function passed `child_process.exec`. Defaults to
     45  a noop.
     46
     47If the configuration is instead a simple `string`, it will be
     48interpreted as a full command itself:
     49
     50```javascript
     51exec: {
     52  echo_something: 'echo "This is something"'
     53}
     54```
    3955
    4056### Command Functions
    4157
    42 If you plan on doing advanced stuff with grunt-exec, you'll most likely be using functions for the `command` property of your exec targets. This section details a couple of helpful tips about command functions that could help make your life easier.
     58If you plan on doing advanced stuff with grunt-exec, you'll most likely be using
     59functions for the `command` property of your exec targets. This section details
     60a couple of helpful tips about command functions that could help make your life
     61easier.
    4362
    4463#### Passing arguments from the command line
    4564
    46 Command functions can be called with arbitrary arguments. Let's say we have the following exec target that echoes a formatted name:
     65Command functions can be called with arbitrary arguments. Let's say we have the
     66following exec target that echoes a formatted name:
    4767
    4868```javascript
    … …  
    6181```
    6282
    63 In order to get `SIMPSON, HOMER` echoed, you'd run `grunt exec:echo_name:homer:simpson` from the command line.
     83In order to get `SIMPSON, HOMER` echoed, you'd run
     84`grunt exec:echo_name:homer:simpson` from the command line.
    6485
    6586### Accessing `grunt` object
    6687
    67 All command functions are called in the context of the `grunt` object that they are being ran with. This means you can access the `grunt` object through `this`.
     88All command functions are called in the context of the `grunt` object that they
     89are being ran with. This means you can access the `grunt` object through `this`.
    6890
    6991### Example
    … …  
    82104      cmd: 'ls -l **'
    83105    },
     106    list_all_files: 'ls -la',
    84107    echo_grunt_version: {
    85108      cmd: function() { return 'echo ' + this.version; }
    … …  
    117140----------
    118141
    119 For transparency and insight into the release cycle, releases will be numbered with the follow format:
     142For transparency and insight into the release cycle, releases will be numbered
     143with the follow format:
    120144
    121145`<major>.<minor>.<patch>`
Note: See TracChangeset for help on using the changeset viewer.