tasks/ directory is a suite of Grunt tasks and their configurations, bundled for your convenience. The Grunt integration is mainly useful for bundling front-end assets (like stylesheets, scripts and markup templates), but it can also be used to run all kinds of development tasks, from browserify compilation to database migrations.
If you haven't used Grunt before, that's OK! For many common use cases, you can get by without customizing or even looking at the files in this folder. If you do need to customize something, be sure to check out the Getting Started guide, as it explains basic concepts like the Gruntfile as well as how to install and use Grunt plugins. Once you're familiar with that process, read on!
The asset pipeline bundled in Sails is a set of Grunt tasks configured with conventional defaults designed to make your project more consistent and productive.
The entire front-end asset workflow in Sails is completely customizable-- while it provides some suggestions out of the box, Sails makes no pretense that it can anticipate all of the needs you'll encounter building the browser-based/front-end portion of your application. Who's to say you're even building an app for a browser?
Sails runs some of these tasks (certain ones in the
tasks/register/ folder) automatically when you run certain commands.
default task (
sails lift --prod
prod task (
build task (
sails www --prod (production)
buildProd task (
You can modify, omit, or replace any of these Grunt tasks to fit your requirements. You can also add your own Grunt tasks- just add a
someTask.js file in the
grunt/config directory to configure the new task, then register it with the appropriate parent task(s) (see files in
Nope! The Sails core team has used Grunt on real-world projects for upwards of 4 years now, and overall it's been a fantastic tool. But we realize it's not for everyone. To disable Grunt integration in Sails, just delete your Gruntfile or disable the Grunt hook.
You can also generate a new Sails app
That's ok! A core tenant of Sails is client-agnosticism-- it's especially designed for building APIs used by all sorts of clients; native Android/iOS/Cordova, serverside SDKs, etc.
You can completely disable Grunt by following the instructions here.
If you still want to use Grunt for other purposes, but don't want any of the default web front-end stuff, just delete your project's
assets folder and remove the front-end oriented tasks from the
grunt/config folders. You can also run
sails new myCoolApi --no-frontend to omit the
assets folder and front-end-oriented Grunt tasks for future projects. You can also replace your
sails-generate-frontend module with alternative community generators, or create your own. This allows
sails new to create the boilerplate for native iOS apps, Android apps, Cordova apps, SteroidsJS apps, etc.
If you know you'll never need any kind of web frontend, you can also generate a new Sails app with
More information on using Grunt to work with static assets: http://gruntjs.com/configuring-tasks