Go to file
Dušan Borovčanin ad80cf868b
Update VerneMQ release (#1593)
Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com>
2022-04-15 15:25:39 +02:00
.github NOISSUE - Fix Swagger UI (#1552) 2022-01-26 10:33:08 +01:00
api MF-1565 - Document Bearer, Thing and Basic Authorization header (#1566) 2022-03-06 01:58:47 +01:00
auth MF-1348 - Add transport errors logging (#1544) 2022-03-03 17:13:46 +01:00
bootstrap MF-1567 - Use Bearer, Thing or Basic scheme in Authorization header (#1568) 2022-03-06 01:49:34 +01:00
certs MF-1565 - Document Bearer, Thing and Basic Authorization header (#1566) 2022-03-06 01:58:47 +01:00
cli MF-1551 - Fix Cobra usage commands and clean unnecessary struct types (#1558) 2022-02-11 13:22:57 +01:00
cmd MF-1582 - Fix lora-adapter MQTT client (#1583) 2022-04-11 13:52:20 +02:00
coap NOISSUE - Fix CoAP adapter (#1572) 2022-03-30 16:52:10 +02:00
consumers NOISSUE - Unify MF_INFLUX_READER_DB_HOST and MF_INFLUX_WRITER_DB_HOST envars (#1585) 2022-03-29 11:53:27 +02:00
docker Update VerneMQ release (#1593) 2022-04-15 15:25:39 +02:00
http MF-1567 - Use Bearer, Thing or Basic scheme in Authorization header (#1568) 2022-03-06 01:49:34 +01:00
internal MF-1567 - Use Bearer, Thing or Basic scheme in Authorization header (#1568) 2022-03-06 01:49:34 +01:00
logger MF-1348 - Add transport errors logging (#1544) 2022-03-03 17:13:46 +01:00
lora MF-1582 - Fix lora-adapter MQTT client (#1583) 2022-04-11 13:52:20 +02:00
metrics NOISSUE - Add exported metrics visualization for grafana (#326) 2018-06-15 17:08:49 +02:00
mqtt MF-1261 - Use StatusUnauthorized for authn and StatusForbidden for authz (#1538) 2022-02-01 17:33:23 +01:00
opcua MF-1348 - Add transport errors logging (#1544) 2022-03-03 17:13:46 +01:00
pkg MF-1567 - Use Bearer, Thing or Basic scheme in Authorization header (#1568) 2022-03-06 01:49:34 +01:00
provision MF-1565 - Document Bearer, Thing and Basic Authorization header (#1566) 2022-03-06 01:58:47 +01:00
readers NOISSUE - Unify MF_INFLUX_READER_DB_HOST and MF_INFLUX_WRITER_DB_HOST envars (#1585) 2022-03-29 11:53:27 +02:00
scripts MF-1565 - Document Bearer, Thing and Basic Authorization header (#1566) 2022-03-06 01:58:47 +01:00
things MF-1575 Add 'Name' field to ListMembers response in things svc (#1576) 2022-03-14 11:03:07 +01:00
tools NOISSUE - Add view and list serials endpoints in certs service (#1483) 2022-01-04 19:42:13 +01:00
twins MF-1348 - Add transport errors logging (#1544) 2022-03-03 17:13:46 +01:00
users MF-1348 - Add transport errors logging (#1544) 2022-03-03 17:13:46 +01:00
vendor Update dependencies (#1564) 2022-02-12 19:07:48 +01:00
.dockerignore Fixed docs instructions in README (#1010) 2020-01-17 14:44:13 +01:00
.gitignore NOISSUE - Clean NginX files, move .gitignores to dirs (#853) 2019-09-16 11:47:34 +02:00
ADOPTERS.md MF-1365 - Add ADOPTERS.md file (#1371) 2021-02-25 13:46:07 +01:00
CHANGELOG.md NOISSUE - Update changelog and readme for release 0.13.0 (#1592) 2022-04-15 12:37:55 +02:00
CONTRIBUTING.md Corrected grammar and rephrased a few sentences to read nicely (#641) 2019-03-07 16:25:37 +01:00
LICENSE Fix copyright year (#1009) 2020-01-17 12:51:01 +01:00
MAINTAINERS Update MAINTAINERS 2018-08-28 22:42:47 +02:00
Makefile MF-1308 - Use IETF Health Check standard (#1541) 2022-01-24 21:18:53 +01:00
README.md NOISSUE - Update changelog and readme for release 0.13.0 (#1592) 2022-04-15 12:37:55 +02:00
api.go MF-788 - Remove date and minimize copyright comments (#876) 2019-10-07 16:14:47 +02:00
auth.pb.go NOISSUE - Listing Policies (#1498) 2021-11-19 14:32:38 +01:00
auth.proto NOISSUE - Listing Policies (#1498) 2021-11-19 14:32:38 +01:00
doc.go MF-788 - Remove date and minimize copyright comments (#876) 2019-10-07 16:14:47 +02:00
env.go MF-435 - Add support for env file loading (#1223) 2020-09-07 15:45:36 +02:00
go.mod Update dependencies (#1564) 2022-02-12 19:07:48 +01:00
go.sum Update dependencies (#1564) 2022-02-12 19:07:48 +01:00
health.go MF-1308 - Use IETF Health Check standard (#1541) 2022-01-24 21:18:53 +01:00
uuid.go NOISSUE - Rename package aliases uuidProvider into uuid (#1323) 2021-01-17 23:12:45 +01: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 and thing (sensor, actuator, 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

  • Multi-protocol connectivity and bridging (HTTP, MQTT, WebSocket and CoAP)
  • Device management and provisioning (Zero Touch provisioning)
  • Mutual TLS Authentication (mTLS) using X.509 Certificates
  • Fine-grained access control (policies, ABAC/RBAC)
  • Message persistence (Cassandra, InfluxDB, MongoDB and PostgresSQL)
  • Platform logging and instrumentation support (Grafana, Prometheus and OpenTracing)
  • Event sourcing
  • Container-based deployment using Docker and Kubernetes
  • LoRaWAN network integration
  • OPC UA integration
  • Edge Agent and Export services for remote IoT gateway management and edge computing
  • SDK
  • CLI
  • Small memory footprint and fast execution
  • Domain-driven design architecture, high-quality code and test coverage

Prerequisites

The following are needed to run Mainflux:

Developing Mainflux will also require:

Install

Once the prerequisites are installed, execute the following commands from the project's root:

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

This will bring up the Mainflux docker services and interconnect them. This command can also be executed using the project's included Makefile:

make run

If you want to run services from specific release checkout code from github and make sure that MF_RELEASE_TAG in .env is being set to match the release version

git checkout tags/<release_number> -b <release_number>
# e.g. `git checkout tags/0.13.0 -b 0.13.0`

Check that .env file contains:

MF_RELEASE_TAG=<release_number>

docker-compose should be used for development and testing deployments. For production we suggest using Kubernetes.

Usage

The quickest way to start using Mainflux is via the CLI. The latest version can be downloaded from the official releases page.

It can also be built and used from the project's root directory:

make cli
./build/mainflux-cli version

Additional details on using the CLI can be found in the CLI documentation.

Documentation

Official documentation is hosted at Mainflux official docs page. Documentation is auto-generated, checkout the instructions on official docs repository:

If you spot an error or a need for corrections, please let us know - or even better: send us a PR.

Authors

Main architect and BDFL of Mainflux project is @drasko.

Additionally, @nmarcetic and @janko-isidorovic assured overall architecture and design, while @manuio and @darkodraskovic helped with crafting initial implementation and continuously worked on the project evolutions.

Besides them, Mainflux is constantly improved and actively developed by @anovakovic01, @dusanb94, @srados, @gsaleh, @blokovi, @chombium, @mteodor and a large set of contributors.

Maintainers are listed in MAINTAINERS file.

The Mainflux team would like to give special thanks to @mijicd for his monumental work on designing and implementing a highly improved and optimized version of the platform, and @malidukica for his effort on implementing the initial user interface.

Professional Support

There are many companies offering professional support for the Mainflux system.

If you need this kind of support, best is to reach out to @drasko directly, and he will point you out to the best-matching support team.

Contributing

Thank you for your interest in Mainflux and the desire to contribute!

  1. Take a look at our open issues. The good-first-issue label is specifically for issues that are great for getting started.
  2. Checkout the contribution guide to learn more about our style and conventions.
  3. Make your changes compatible to our workflow.

We're Hiring

You like Mainflux and you would like to make it your day job? We're always looking for talented engineers interested in open-source, IoT and distributed systems. If you recognize yourself, reach out to @drasko - he will contact you back.

The best way to grab our attention is, of course, by sending PRs 😎.

Community

License

Apache-2.0

FOSSA Status