grunt-raind

Automatically restarts the RAIN server if CSS, templates or server scripts are changed. To be used as watch task in conjunction with grunt-contrib-watch.

Getting started (for RAIN developers)

This plugin requires Grunt ~0.4.0 and plugin grunt-contrib-watch to be used meaningfully.

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins.

Installation

As this plugin is not published in npm, you have to add it with its repository URL (together with grunt-contrib-watch) as development dependency to your RAIN project's package.json.

Example:

  "devDependencies" : {
    "grunt" : "0.4.x",
    "grunt-raind" : "git://github.com/d-werner/grunt-raind.git",
    "grunt-contrib-watch" : "*"
  }

Install grunt and the plugins with this command in your project root directory.

npm install

Configuring Grunt

The easiest way would be to copy this example Gruntfile in your project root directory or merge it with your existing Gruntfile.

Alternatively you can create or adapt your Gruntfile like this:

• Enable the plugins with these lines of code:

grunt.loadNpmTasks("grunt-contrib-watch");
grunt.loadNpmTasks("grunt-raind");

• Setup a watch task that executes task raind-restart and watches for file changes in your components' CSS, template and server directories.

 watch : {
    raind : {
      files : [ "components/**/client/css/**/*.css", "components/**/client/templates/**/*.html", "components/**/server/**/*.js", "conf/*.conf" ],
      tasks : "raind-restart"
    }
  }

• As you want the RAIN server to be up and running immediately, you need to register a combined task that first executes raind-restart to start the server and calls the previously setup watch task afterwards.

grunt.registerTask("raind", ["raind-restart", "watch:raind"]);

Usage

Call Grunt with the combined task starting the RAIN server and the watch task in your project root directory. According to the example Gruntfile, this command would be:

grunt raind

Terminating the watch process will also terminate the RAIN server.

Server logs

The server's STDOUT and STDERR are written into raind.log in the project root directory.

Why is the server not restarted on CSS or template changes?

If the file changes do not trigger the watch task, this could be due to the editor's "safe write" mechanism (s. watch issue 13). It is possible to disable this feature in IntelliJ IDEs by unchecking IDE Settings > General > Use "safe write"