Go to file
Aleksandar Novaković 97c2d9c30a NOISSUE - Update dashflux port on kubernetes configuration (#317)
* Update dashflux port on kubernetes configuration

Signed-off-by: Aleksandar Novakovic <aleksandar.novakovic@mainflux.com>

* Remove target port from dashflux config

Signed-off-by: Aleksandar Novakovic <aleksandar.novakovic@mainflux.com>
2018-05-29 10:47:27 +02:00
.github MF-199 - Create documentation skeleton (#218) 2018-04-08 23:03:12 +02:00
cmd MF-236 - Add support for storing messages in InfluxDB (#283) 2018-05-21 16:28:52 +02:00
dashflux MF-282 - Rename clients to things in Dashflux (#305) 2018-05-24 15:26:03 +02:00
docker Add version endpoint to nginx configuration (#316) 2018-05-28 19:20:17 +02:00
docs MF-269 - Replace UUID with BIGSERIAL as primary key (#291) 2018-05-21 12:51:46 +02:00
http MF-236 - Add support for storing messages in InfluxDB (#283) 2018-05-21 16:28:52 +02:00
k8s NOISSUE - Update dashflux port on kubernetes configuration (#317) 2018-05-29 10:47:27 +02:00
load-test NOISSUE - Add test suite for WebSocket adapter (#299) 2018-05-25 11:53:45 +02:00
logger MF-174 - Add logger interface and go-kit logger implementation (#212) 2018-04-04 10:15:23 +02:00
mqtt MF-269 - Replace UUID with BIGSERIAL as primary key (#291) 2018-05-21 12:51:46 +02:00
normalizer NOISSUE - Emit non-SenML messages (#279) 2018-05-14 22:15:12 +02:00
things MF-269 - Replace UUID with BIGSERIAL as primary key (#291) 2018-05-21 12:51:46 +02:00
users MF-269 - Replace UUID with BIGSERIAL as primary key (#291) 2018-05-21 12:51:46 +02:00
vendor MF-236 - Add support for storing messages in InfluxDB (#283) 2018-05-21 16:28:52 +02:00
writers NOISSUE - Remove redundant error check (#292) 2018-05-21 20:11:04 +02:00
ws NOISSUE - Fix channel closing bug in WebSocket adapter (#309) 2018-05-28 12:47:20 +02:00
.gitignore MF-199 - Create documentation skeleton (#218) 2018-04-08 23:03:12 +02:00
Gopkg.lock MF-236 - Add support for storing messages in InfluxDB (#283) 2018-05-21 16:28:52 +02:00
Gopkg.toml MF-236 - Add support for storing messages in InfluxDB (#283) 2018-05-21 16:28:52 +02:00
LICENSE MF-199 - Create documentation skeleton (#218) 2018-04-08 23:03:12 +02:00
MAINTAINERS Remove lora-related artifacts 2017-09-22 23:17:04 +02:00
Makefile MF-236 - Add support for storing messages in InfluxDB (#283) 2018-05-21 16:28:52 +02:00
README.md Fix http publish example in docs (#231) 2018-04-18 16:49:10 +02:00
api.go NOISSUE - Handle authorization errors other than unauthorize (#264) 2018-05-11 16:37:32 +02:00
doc.go Use PostgreSQL as primary persistence solution (#175) 2018-03-11 18:06:01 +01:00
env.go MF-164 - Split manager service (#266) 2018-05-10 23:53:25 +02:00
internal.proto MF-269 - Replace UUID with BIGSERIAL as primary key (#291) 2018-05-21 12:51:46 +02:00
message.proto MF-269 - Replace UUID with BIGSERIAL as primary key (#291) 2018-05-21 12:51:46 +02:00
mkdocs.yml MF-134 - Evaluate system's performance (#225) 2018-04-23 15:13:43 +02:00
publisher.go MF-164 - Split manager service (#266) 2018-05-10 23:53:25 +02:00
version.go NOISSUE - Rename clients to things (#281) 2018-05-15 17:13:09 +02:00

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