Issue #4 resolved
Remco Janssen created an issue
  1. Add deployment tasks Dev, Stage, Production
  2. Add build tasks Debug, Release

Comments (5)

  1. Remco Janssen reporter

    @Rafi Khan What are the needs for every task described above? For instance, would the release task concat and uglify to the root only?

  2. Rafi Khan

    As of right now I think we should have the following:

    gulp or gulp debug will do a debug build which will:

    1. Stitch the scripts
    2. Copy to the proper location for local development/testing

    gulp release will do a release/dev build:

    1. Stitch, remove debug code, uglify everything
    2. Copy to the proper location for local development/testing
    3. Package (i.e. zip) the script, a readme file and put it into something like a ./dist directory.

    Later, when we need to integrate a server (if ever) I see 3 other targets getting introduced:

    • gulp dev which deploys a debug build to a dev server for local distribution.
    • gulp stage which deploys a release or debug build to a staging server for smoke testing prior to 'going live'.
    • gulp prod which deploys a release build to a prod server for release.
  3. Log in to comment