This configuration allows you to create application development environment on your local machine with VirtualBox and Vagrant so that you can try MOAT IoT example apps shortly.
The environment is built on the VirtualBox image and never affects your current working environment.
You are now free from performing a bunch of downloading and installation tasks for setup.
At first, please read this page and install Vagrant along with VirtualBox.
After installing Vagrant and VirtualBox, then checkout this project:
$ git clone https://github.com/inventit/moat-iot-get-started-vagrant.git
$ wget https://github.com/inventit/moat-iot-get-started-vagrant/archive/master.zip
Finally, enter the command on the terminal to setup (on the checkout root directory):
moat-iot-get-started-vagrant:$ vagrant up
NOTE that this would take at least 20 minutes or more depending on the network state at first time. After the first trial, it would take 5 or more.
In order to set up the example applications, let's go to the tutorial.
If your machine uses HTTP web proxy, do the following steps.
Install the proxy plugin.
$ vagrant plugin install vagrant-proxyconf
Then launch the vagrant.
$ VAGRANT_HTTP_PROXY=http://host:port/ vagrant up
Once vagrant up is completed, vagrant ssh and run the following command;
~/download-platform-tools.sh
in order to install Android's platform-tools. This should be performed manually because the command asks you proxy settings interactively.
In some cases, npm package installation may cause timeout. You can choose HTTP rather than HTTPS for downloading packages via npm, which should be faster (insecure though).
After completing vagrant up command, the console complains as follows:
==> default: Configuring proxy for npm...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
npm config set proxy http://proxyhost:proxyport/
Stdout from the command:
Stderr from the command:
stdin: is not a tty
bash: line 2: npm: command not found
You can ignore the message since npm is properly installed despite the error.
This tool does NOT perform;
Building MOAT IoT example apps but checking out
Again, please follow the instruction for building.
These scripts install the following modules:
apt-getInstallationopenjdk-6-jdk, Java Development Kit 6git, Gitbuild-essential, Package building librarieslibsqlite3-dev, Used by Railsruby2.1, Ruby 2.1.0ruby2.1-dev, Header files for Ruby 2.1.0ruby-bundler, RubyGems management toolrake, Ruby Makerails, Ruby on Rails- Binary Installation
- Apache Maven 3.0.5, Java Building Tool
- Android SDK r21.0.1 and Platform libraries(API Level 16)
- Source Installation
- Node.js v0.10.26
nvm, Node Version Managernpm, Node Package ManagernpmInstallationmoat, MOAT js unit testing librarysinon, Mock/Stub testing librarynodeunit, Unite testing library
and
- You can choose 64bit based Ubuntu 12.04 but it takes longer time to
vagrant upbecause of more libraries are required than 32bit Ubuntu in Android SDK installation
All program source codes are available under the MIT style License.
The use of IIDN service requires our term of service.
Copyright (c) 2014 Inventit Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
1.0.13 : September 19, 2014
- Fixes an issue where android build-tools is always missing after finishing Vagrant up/provision
1.0.12 : September 19, 2014
- Fixes an issue where the latest nvm doesn't work with the nodejs recipe
1.0.11 : May 29, 2014
- Fixes an issue where iidn-cli project is not properly cloned
1.0.10 : May 28, 2014
- Fixes an issue where nvm failed to be installed because of a lack of HTTP redirect support
1.0.9 : April 5, 2014
- HTTP web Proxy support
- Adds a new option to enable/disable SSL for npm (SSL enabled by default)
1.0.8 : March 14, 2014
- Fixes an issue where android platform sdk is not accessible from a maven android plugin
- Fixes an issue Chef-solo process is killed unexpectedly because of out of memory error
1.0.7 : March 13, 2014
- Supports Vagrant 1.5.0. Older versions of Vagrant are no longer supported
- Adds a new resource to install rails
- Ruby is upgraded to 2.1
- Node.JS is upgraded to 0.10.26
1.0.6 : February 19, 2013
- Fixes an issue where creating a project directory is skipped because of duplicate recipe resource name
1.0.5 : February 15, 2013
- Adds a new recipe to install node-v0.8.19
1.0.4 : February 13, 2013
- Fixes an issue where port forwarding settings is missing
1.0.3 : February 13, 2013
- Fixes issues where re-launching a created image fails on errors
1.0.2 : February 13, 2013
- Adds environment variables used in the instruction to .bashrc
1.0.1 : February 12, 2013
- Fixes an issue where android API level 16 is not installed
1.0.0 : February 12, 2013
- Initial Release.