apiotics 0.1.120 → 0.1.121

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 41c0adbd3fd359d4d9e2afd8211e5c6103dd4332
-  data.tar.gz: c7c27ed4fb0136e8806c88541a442ab97cefe061
+  metadata.gz: fa2eec379a6740eea0ba092219a190d225a0af57
+  data.tar.gz: 92859fb86b4845505d91063342b9d9b0bf25388b
 SHA512:
-  metadata.gz: 13806bd52c115a6083ba70594b8168423a2eb12c3e7f28d02e90cfa2eb552c71b3753fefa19f5e65bb9c483482d324d4d97f6d6b923b9cc2839cfb8e0c28738f
-  data.tar.gz: 6e082927f31b74bf4880acefe742bbeb50531538b2893070fac684cb12ad414d3d19480b27884d78d014a768f272a9471d79b7447446df91fc2ff4024386995b
+  metadata.gz: fdce7b9e0b50718449f61148c31584fb173fab5a60ada76c82b65c65cf1af45c23d8528e9d3a92559138ffa8cd609b3715c5d66a10076011548772b42517a26e
+  data.tar.gz: 2160936b365e57766ebe48dd99fb7b81c2f3f1e675363231f9ebdc837d1c1507f36a9396a2ce208926d08a66a478b94643e0f19fa7320553fdd4e53b1c1c4b23

data/README.md

@@ -18,7 +18,7 @@ And then execute:
 $ bundle
 $ rails generate apiotics:install
 ```
-On the Apiotics portal located at www.apiotics.com, you can create a Hive for your project. Hives have Workers (each type of IoT device in your project will have a corresponding worker in the Hive).  Workers have Drivers and, optionally, Scripts.  Drivers and Scripts have interfaces.  An example worker might be a Thermostat.  The Thermostat has a Control Script with two interfaces: temperature and target temperature.  If you set the target temperature to 72 and the temperature is 65, the Thermostat will turn the heat on.  We'll use this example again and flesh it out below.
+On the Apiotics portal located at portal.apiotics.com, you can create a Hive for your project. Hives have Workers (each type of IoT device in your project will have a corresponding worker in the Hive).  Workers have Drivers and, optionally, Scripts.  Drivers and Scripts have interfaces.  An example worker might be a Thermostat.  The Thermostat has a Control Script with two interfaces: temperature and target temperature.  If you set the target temperature to 72 and the temperature is 65, the Thermostat will turn the heat on.  We'll use this example again and flesh it out below.
 
 Once you have created a Hive, it will give you a public and a private API key.  Best practice is to set environment variables in your development, test and production environments to equal these API keys.  Then, set config.public_key and config.private_key in config/initializers/apiotics.rb to those environment variables.  You can enter the API keys directly into the configuration file, but you should only do this if you never plan to put your Rails application and Hive into production, as it is a significant security risk.
 

data/lib/apiotics/configuration.rb

@@ -11,7 +11,7 @@ module Apiotics
       @local_port = 8001
       @server = "rgs.microarx.com"
       @server_port = 8000
-      @portal = "https://www.apiotics.com/"
+      @portal = "https://portal.apiotics.com/"
       @push = false
       @tls = true
       @verify_peer = true

data/lib/apiotics/version.rb

@@ -1,3 +1,3 @@
 module Apiotics
-  VERSION = '0.1.120'
+  VERSION = '0.1.121'
 end

data/lib/generators/apiotics/initializer/templates/apiotics.rb.erb

@@ -14,7 +14,7 @@ Apiotics.configure do |config|
   config.server_port = 8000
   
   # The Apiotics portal.  Again, very few reasons to change this.
-  config.portal = "https://www.apiotics.com/"
+  config.portal = "https://portal.apiotics.com/"
   
   # Secure communications parameters.  The defaults should be appropriate for almost all use cases.
   config.tls = true

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: apiotics
 version: !ruby/object:Gem::Version
-  version: 0.1.120
+  version: 0.1.121
 platform: ruby
 authors:
 - MicroArx Corporation
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-01-08 00:00:00.000000000 Z
+date: 2018-01-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails