Version 1.0.0: Feature Complete

This is the first feature complete release of Deploy Goon.

This release amplifies the existing functionality by doing the following:

• NEW Notifications.
• NEW IP Whitelisting.
• NEW Test coverage.
• FIXED Bugs related to polluting state between instances of DeployJob and DeployGoonConfiguration.

Enjoy!

Initial NPM Release

This is the initial release of deploy-goon to npm, and the first release that is useful in terms of functionality. It's not yet feature complete, and it is still very rough around the edges, but it's complete enough for me to be interested in using in my production environments. We still need to add more detailed instructions on how to use it, but the gist is that you'll want to define a json file that describes your build. For example:

{
  "slug": "baconsauce",
  "description": "An example deployment allowable from localhost.",
  "ipWhitelist": ["127.0.0.1"],
  "deployActions": [
    {
      "name": "Echo Lo",
      "command": "echo",
      "arguments": ["lo"]
    }
  ],
  "notifictionSettings": {
    "notify": "always",
    "email": "matt@sauce.com"
  }
}

Then you'll want to install deploy-goon using npm on your machine:

$ npm install -g deploy-goon

Add the json file for your project to deploy goon:

$ deploygoon add path/to/project/json/file.json

Then start the daemon.

$ sudo deploygoon start

Then you should be able to send HTTP requests to trigger deploys. If your slug is baconsauce as it is in the example above, you should be able to trigger a deploy with the following command:

$ curl http://localhost:9090/baconsauce

I'm sure there are bugs / inconsistencies I haven't thought of yet. Please give it a test and let me know what you find.