iotservice Download - iotservice Source code download

iotservice

Other categories

1.0.0

Download

Chinese | English

Proton-IotService

Proton-IotService is an open source Iot platform that integrates the device management backend and the device is connected to the SDK. It is a complete IoT solution that can be used to quickly build IoT-related business systems.

Rapid deployment

If you want to experience the project quickly, you can directly use docker's one-click deployment capabilities, refer to the deployment manual.

Of course, you can also compile the project from scratch and deploy it, refer to the compilation manual

Development Model

If you want to quickly enter the development stage, you can execute the following command

docker run --name=aproton-dev- $( whoami ) -p8080:8080 -p3306:3306 -p9301:9301 
    -v $PWD :/root/iotservice -w /root/iotservice -it 
    aproton/iotservice-dev:latest /bin/bash

Core abilities

Device management backend

The device management backend API interface is developed based on Laravel, and the front end adopts VUE development.

Sample diagram

Device access API

The platform provides a set of API interfaces for IOT device access, including device authentication, device attributes, positioning, OTA and other API interfaces.

Interface documentation reference: API

Device SDK

The platform also provides a set of SDKs for fast access devices, developed using C. The code is to be combined into quark in other projects.

Architectural design

To be supplemented

Directory structure

 +
|--- backend           # 管理台API以及设备API
|--+ extenstion        
|  |-- eletron         # PHP扩展
|--- website           # 管理台前端页面
|--- build             # 编译相关代码
|--- deploy            # 部署相关代码

Open source contribution

Branch planning

The project plan adopts five types of branching models;

master/main branch: core development branch, where can all new code be entered here
Release branch: If there is a stable version released, a release branch will be pulled out separately, such as release/v1.0; the bug fix on the branch needs to be merged into the release branch and the master branch at the same time.
feature branch: If there is new function development, pull a branch from master, develop and merge it into master
Bug branch: If you need to fix the bug, you can pull a branch separately from the master(or feature) branch, develop and merge it.
Large version branch (removed in the future): If the functions that need to be developed are relatively large, such as the current state uses dev1.0 as the branch, after joining the master in the future, this mode will be discarded and the first 4 branches will be adopted.

Contribution code

First checkout a new branch from the master branch, format: feature/username_description; develop and submit PR based on the new branch, and after CR is passed, you can join