Industrial IoT Messaging and Device Management Server
Clone or download
blokovi and anovakovic01 NOISSUE - Add pull request template (#414)
* Add pull request template

Signed-off-by: Ivan Milošević <iva@blokovi.com>

* Fix formatting in docs

Signed-off-by: Ivan Milošević <iva@blokovi.com>

* Fix link for contributing guidelines

Signed-off-by: Ivan Milošević <iva@blokovi.com>
Latest commit 6eade2c Oct 4, 2018
Permalink
Failed to load latest commit information.
.github NOISSUE - Add pull request template (#414) Oct 4, 2018
cli MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
cmd MF-404 - InfluxDB batch size and timeout zero values (#411) Oct 1, 2018
dashflux MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
docker NOISSUE - Influxdb batch add (#394) Sep 22, 2018
docs NOISSUE - Add pull request template (#414) Oct 4, 2018
http MF-379 - Log Level Option (#402) Sep 26, 2018
k8s NOISSUE - Influxdb batch add (#394) Sep 22, 2018
load-test Bump version to 0.5.1 (#385) Sep 4, 2018
logger Fixing level_test.go (#406) Sep 26, 2018
metrics NOISSUE - Add exported metrics visualization for grafana (#326) Jun 15, 2018
mqtt Update mqtt to mqtt communication to support full protocol (#408) Sep 30, 2018
normalizer MF-379 - Log Level Option (#402) Sep 26, 2018
readers MF-379 - Log Level Option (#402) Sep 26, 2018
scripts Initial user, device, channel provisioning script used to speed up te… Aug 27, 2018
things MF-384 - Add test for Redis cache (#405) Sep 30, 2018
users MF-379 - Log Level Option (#402) Sep 26, 2018
vendor MF-382 - Improve performance by adding Redis cache for message auth (#… Sep 4, 2018
writers MF-404 - InfluxDB batch size and timeout zero values (#411) Oct 1, 2018
ws MF-379 - Log Level Option (#402) Sep 26, 2018
.gitignore MF-363 - Add compiled .proto files (#364) Aug 24, 2018
Gopkg.lock MF-382 - Improve performance by adding Redis cache for message auth (#… Sep 4, 2018
Gopkg.toml MF-216 - Integrate Bashflux into monorepo (#308) Jul 11, 2018
LICENSE MF-199 - Create documentation skeleton (#218) Apr 8, 2018
MAINTAINERS Update MAINTAINERS Aug 28, 2018
Makefile NOISSUE - Dev dockers (#392) Sep 19, 2018
README.md Fix http publish example in docs (#231) Apr 18, 2018
api.go MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
doc.go MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
env.go MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
internal.pb.go MF-363 - Add compiled .proto files (#364) Aug 24, 2018
internal.proto MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
message.pb.go MF-363 - Add compiled .proto files (#364) Aug 24, 2018
message.proto MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
mkdocs.yml NOISSUE - Add Development Guide doc (#351) Aug 16, 2018
package-lock.json NOISSUE - Add system run script (#350) Aug 16, 2018
publisher.go MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
topics.go MF-325 - Add SPDX license and copyright headers (#362) Aug 26, 2018
version.go Bump version to 0.5.1 (#385) Sep 4, 2018

README.md

Mainflux

build go report card coverage license chat

banner

Mainflux is modern, scalable, secure open source and patent-free IoT cloud platform written in Go.

It accepts user, device, and application connections over various network protocols (i.e. HTTP, MQTT, WebSocket, CoAP), thus making a seamless bridge between them. It is used as the IoT middleware for building complex IoT solutions.

For more details, check out the official documentation.

Features

  • Protocol bridging (i.e. HTTP, MQTT, WebSocket, CoAP)
  • Device management and provisioning
  • Fine-grained access control
  • Platform logging and instrumentation support
  • Container-based deployment using Docker

Quickstart

Before proceeding, install the following prerequisites:

Once everything is installed, execute the following commands from project root:

docker-compose -f docker/docker-compose.yml up -d

Contributing

Thank you for your interest in Mainflux and wish to contribute!

  1. Take a look at our open issues.
  2. Checkout the contribution guide to learn more about our style and conventions.
  3. Make your changes compatible to our workflow.

Community