Build process

overleaf/web uses [Grunt](http://gruntjs.com/) to build its front-end related assets.

Image processing tasks are commented out in the gruntfile and the needed packages aren't presently in the project's `package.json`. If the images need to be processed again (minified and sprited), start by fetching the packages (`npm install grunt-contrib-imagemin grunt-sprity`), then *decomment* the tasks in `Gruntfile.coffee`. After this, the tasks can be called (explicitly, via `grunt imagemin` and `grunt sprity`).

New Docker-based build process

Note that the Grunt workflow from above should still work, but we are transitioning to a

Docker based testing workflow, which is documented below:

*Ideally the app would run in Docker like the tests below, but with host networking not supported in OS X, we need to run it natively until all services are Dockerised.*

// Should javascript assets be served minified or not. Note that you will

// need to run `grunt compile:minify` within the web-sharelatex directory

// to generate these.