andreptb/grunt repository overview

⁠Supported tags and respective Dockerfile links

• 0.1.13, 0.1.13-node-5.1.0, latest (grunt/Dockerfile)⁠

⁠Why use a task runner?

In one word: automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it through a Gruntfile⁠, a task runner can do most of that mundane work for you—and your team—with basically zero effort.

⁠Why use Grunt?

The Grunt ecosystem is huge and it's growing every day. With literally hundreds of plugins to choose from, you can use Grunt to automate just about anything with a minimum of effort. If someone hasn't already built what you need, authoring and publishing your own Grunt plugin to npm is a breeze. See how to get started⁠.

⁠How to use this image

The most straightforward way to use this image is to run the following (considering that $PWD directory contains a validhttp://gruntjs.com/getting-started#the-gruntfile

• Download npm⁠ dependencies:

docker run -it --rm --name grunt-task -v $PWD:/data grunt

• Download bower⁠ dependencies:

docker run -it --rm --name grunt-task -v $PWD:/data bower install

• Run a grunt⁠ task:

docker run -it --rm --name grunt-task -v $PWD:/data grunt

⁠What are the contents of this image ?

• Doesn't extend library/node⁠. Uses dockerfile/debian:jessie⁠ and installs NodeJS⁠ in a similar fashion. However only images for version 5.x is provided.
• Provides Bower⁠ package manager.
• Provides Ruby⁠ with SASS⁠ CSS compiler.

⁠License

View license information for the software contained in this image:

• Node⁠.
• GruntJS⁠.
• Bower⁠.
• SASS⁠.
• Ruby⁠;

⁠Supported Docker versions

This image is officially supported on Docker version 1.7.0.

⁠Issues

If you have any problems with or questions about this image, please contact me through a GitHub issue⁠.