Difference between revisions of "Five easy ways to install AGILE (running the default stack)"

From AGILE IoT Wiki
Jump to: navigation, search
Line 5: Line 5:
 
# '''ResinOS based managed solution:''' useful for large scale deployments with fleet management services, or when cloud based management is required.
 
# '''ResinOS based managed solution:''' useful for large scale deployments with fleet management services, or when cloud based management is required.
 
# '''Building and installing from source'''
 
# '''Building and installing from source'''
 +
 +
 +
== ResinOS based gateway with local management ==
 +
* Download ResinOS from https://resinos.io/#downloads-raspberrypi
 +
* (optional) Install resin-cli
npm i -g resin-cli
 +
* (optional) Configure the dowloaded SD image (only required if connecting to WiFi)
resin local configure resin.img
 +
* Burn image to microSD (we recommend Etcher.io)
 +
* Clone agile-stack
git clone https://github.com/agile-iot/agile-stack && cd agile-stack
 +
* Configure the stack by creating and editing the .env file 
cp .env.example .env
 +
* After powering on the GW with the microSD card, Initialise AGILE 
docker-compose up -d
 +
* Connect to http://resin.local:8000
 +
* for further details, see https://github.com/Agile-IoT/agile-stack/

Revision as of 09:50, 10 April 2018

AGILE support different use cases, and correspondingly several installation methods:

  1. ResinOS based gateway with local management: select this option if a robust OS is required, one of the supported GW platforms are used, but remote cloud based management is not needed. AGILE will be running on the gateway machine, but docker-compose will be run from a local management machine. The management machine can be any PC, it is only used to configure the GW at deployment, and later, if necessary, to update services.
  2. Raspbian based standalone gateway: only available for Raspberry Pi (1, 2, 3, 3+), this type of deployment is useful for those who are used to Raspbian, would like to run other services next to AGILE, and are not afraid of logging in to the gateway with SSH to manage things.
  3. Docker and docker-compose based installation: Useful for any other platform not supported by the above methods (e.g. Linux based PCs, OS X), or when deploying AGILE code on an existing server. It is also useful for testing the AGILE stack without a dedicated gateway (i.e. on a laptop).
  4. ResinOS based managed solution: useful for large scale deployments with fleet management services, or when cloud based management is required.
  5. Building and installing from source


ResinOS based gateway with local management