text: GitHub - dbashford/mimosa-web-package: Web App Packaging Module for Mimosa
  dbashford / mimosa-web-package
  Web App Packaging Module for Mimosa
  This is a Mimosa module for packaging web applications. It assumes that the mimosa-server module is also being used.
  For information regarding packaging in Mimosa, see http://mimosa.io/commands.html#package
  Add web-package as a string to your list of modules in the mimosa-config. When Mimosa starts up, it will install the module for you.
  If you are running mimosa build with the --package flag, mimosa-web-package will:
  Remove the directory at webPackage.outPath if it already exists
  Copy your entire project to the webPackage.outPath folder, omitting anything you have listed in webPackage.exclude
  Re-write the package.json to not include any mimosa packages in the package.json depedencies array.
  Write the parts of the fully-resolved and blown out mimosa-config that pertain to the server to the webPackage.outPath as config.js. Will set some config values, like live reload to production level settings. Will also turn normally absolute mimosa-config paths relative. To accommodate app hosting solutions like Heroku, config.js also re-figures the location of public assets.
  Write a simple app.js file to webPackage.outPath. app.js exists to be a starting point for your app when Mimosa is not available to invoke your server. It simply reads the config, and calls your server.startServer method passing the config.
  runs NPM install from inside the webpackage.outPath. The --production flag is used to avoid installing any packages in your package.json devDependencies. If your production app actually depends on any packages listed there, they should really be in dependencies.
  By default a .tar.gz will be created for your packaged application. If archiveName is set to a .zip file, a .zip file will be created instead.
  What you get as a result is an application that runs without Mimosa's aid by simply executing node app.js, as well as an archive file (.tar.gz/.zip) of the codebase.
  If tar/zip isn't available as a command line utility on your system, no tar/zip file will be created.
  If your application is using Mimosa's default server rather than a server of your own, web-package will not write an app.js and will not execute npm install.
  webPackage:
  archiveName: "app"
  configName: "config"
  outPath: "dist"
  exclude: ["README.md","node_modules","mimosa-config.coffee","mimosa-config.js","assets",".git",".gitignore","mimosa-config-documented.coffee",".mimosa","bower.json"]
  archiveName: a string, the name of the output .tar.gz/.zip file. No archive will be created if archiveName is set to null. A .zip will only be created if the archiveName ends in .zip. Otherwise a tar file is assumed. The following rules only apply to .tars. If the default is changed away from app, web-package will use the changed config setting. If the default is left alone, web-package will check the for a name property in the package.json, and if it exists, it will be used. If the default is left as app, and there is no package.json.name property, the default is used.