homebridge - npm Package Compare versions

Comparing version 0.2.18 to 0.2.19

lib/cli.js

		@@ -20,3 +20,3 @@ var program = require('commander');
		.option('-D, --debug', 'turn on debug level logging', function() { require('./logger').setDebugEnabled(true) })
		.option('-I, --insecure', 'allow insecure access to homebridge', function() { insecureAccess = true; })
		.option('-I, --insecure', 'allow unauthenticated requests (for easier hacking)', function() { insecureAccess = true })
		.parse(process.argv);
		@@ -27,3 +27,15 @@

		new Server(insecureAccess).run();
		var server = new Server(insecureAccess);

		var signals = { 'SIGINT': 2, 'SIGTERM': 15 };
		Object.keys(signals).forEach(function (signal) {
		process.on(signal, function () {
		log.info("Got %s, shutting down Homebridge...", signal);

		// FIXME: Shut down server cleanly
		process.exit(128 + signals[signal]);
		});
		});

		server.run();
		}

lib/server.js

		@@ -28,2 +28,7 @@ var path = require('path');

		// Server is "secure by default", meaning it creates a top-level Bridge accessory that
		// will not allow unauthenticated requests. This matches the behavior of actual HomeKit
		// accessories. However you can set this to true to allow all requests without authentication,
		// which can be useful for easy hacking. Note that this will expose all functions of your
		// bridged accessories, like changing charactersitics (i.e. flipping your lights on and off).
		this._allowInsecureAccess = insecureAccess \|\| false;
		@@ -30,0 +35,0 @@ }

package.json

		{
		"name": "homebridge",
		"description": "HomeKit support for the impatient",
		"version": "0.2.18",
		"version": "0.2.19",
		"scripts": {
		@@ -34,5 +34,5 @@ "dev": "DEBUG=* ./bin/homebridge -D -P example-plugins/ \|\| true"
		"commander": "2.8.1",
		"hap-nodejs": "0.2.3",
		"hap-nodejs": "0.2.5",
		"semver": "5.0.3"
		}
		}

New alerts