Paul Masurel  committed 2bc0e3c

Edited online

  • Participants
  • Parent commits 8c4c8f4

Comments (0)

Files changed (1)

 But most importantly, if one queries for a **something.js** (respectively **something.css**) file, tumbler will look for **** (respectively **something.less**)  file and will serve the result of its compilation.
-You may also define js bundles, that is a bunch of javascript that you need to import together.
-The bundle files should have the form : filename.js.bundle and should contain the relative path of all the js file to include.
+== Javascript Bundle ==
+Let's suppose your web page use a lot of javascript files.
+Ultimately you want them to be deployed as one big javascript files to reduce the number of request.
+To do so, you can define a javascript bundle.
+Create a {{{myproject.js.bundle}}} containing the javascript you want to include, one on each lines.
 When the browser fetches filename.js, tumbler's response will differ depending on its mode:
-   -  tumbler serve -m debug
+   *  {{{tumbler serve -m debug}}}
       All the files will be included as script tag in the dom.
       This makes debugging easier as the 
-   -  tumbler serve -m concat
+   *  {{{tumbler serve -m concat}}}
       The server will serve a big file, concatenation of all the other files.
-   -  tumbler serve -m release
-      The file are compressed and optimized using uglified js.
+   *  {{{tumbler serve -m release}}} The file are compressed and optimized using uglified js.
+== Deployment  ==
+Tumbler is not intended for production use. 
+You probably want to compile all your files before putting them on a performant static file server.
-Try tumbler --help for more options.
+To do so, create a {{{project.targets}}} file, you can then deploy by running
+{{{ tumbler deploy -t project.targets -d destination -m release }}}