822c1baf85
* update http messaging to mproxy Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix import path for mproxy module The import path for the mproxy module has been updated to github.com/sammyoina/mproxy v0.0.0-20231005134356-c44220b46ea0. This change ensures that the correct version of the module is used. This commit fixes the import path for the mproxy module, updating it to github.com/sammyoina/mproxy v0.0.0-20231005134356-c44220b46ea0. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix inconsistent variable naming in streams_test.go The variable "defaultTimout" was misspelled and should be "defaultTimeout". Also, the unused variable "configList" was removed. - Fix variable name "defaultTimout" to "defaultTimeout" - Remove unused variable "configList" Signed-off-by: SammyOina <sammyoina@gmail.com> * update mproxy Signed-off-by: SammyOina <sammyoina@gmail.com> * update mproxy Signed-off-by: SammyOina <sammyoina@gmail.com> * use auth connect Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix incorrect HTTP status code in endpoint_test.go The previous commit introduced a mistake in the HTTP status code used in the endpoint_test.go file. The status code http.StatusUnauthorized was changed to http.StatusBadGateway. This commit corrects the status code to http.StatusBadRequest. This commit also includes a minor change in the things.go file. It adds three lines of code to the Authorize function. These changes ensure that the test cases and authorization logic are aligned with the correct HTTP status codes. Signed-off-by: SammyOina <sammyoina@gmail.com> * fix errors Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix import formatting in message_test.go The import statements in message_test.go were not properly formatted. This commit fixes the formatting by organizing the imports and removing unnecessary commented code. - Import statements were organized and grouped together. - Unnecessary commented code was removed. This commit resolves the import formatting issue in message_test.go, ensuring that the codebase adheres to proper formatting conventions. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix import order and add missing import in endpoint_test.go The import order in the `endpoint_test.go` file has been fixed, and the missing import for `mainflux/mainflux` has been added. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix targetHTTPHost value in main.go and remove commented code in endpoint_test.go Summary: Fix targetHTTPHost value and remove commented code Body: - In main.go, fix the value of targetHTTPHost to "http://localhost" - In endpoint_test.go, remove commented code This commit fixes the targetHTTPHost value in main.go and removes unnecessary commented code in endpoint_test.go. The targetHTTPHost value was previously empty and has been updated to "http://localhost" to correctly specify the target HTTP host. Additionally, the commented code in endpoint_test.go has been removed for cleaner code. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix typo in log statement Signed-off-by: SammyOina <sammyoina@gmail.com> * Refactor HTTP server startup logic Refactor the logic for starting the HTTP server in the `main.go` file. Instead of directly starting the server and logging the server details, the code now uses a goroutine to start the server. This change improves code readability and maintainability. The commit message follows the best practices for writing commit messages. It starts with a succinct one-line summary of the changes, which is no longer than 50 characters. The summary is capitalized and written in the imperative mood. The summary is followed by a more detailed description, separated by a blank line. The body of the message provides context and reasoning behind the changes. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix import and variable assignment in main.go The import "github.com/mainflux/mainflux/pkg/messaging" was removed and the variable assignment for "h" in main() was updated to remove the unnecessary slice brackets. This commit fixes the import and variable assignment in main.go to ensure proper functionality. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix typo in function name The function name "newProxyHTPPServer" was misspelled and has been corrected to "newProxyHTTPServer". This commit fixes the typo in the function name. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix Docker clean command in Makefile The Docker clean command in the Makefile has been fixed to include the Docker profile and project name. This ensures that all containers, networks, volumes, and images created by the "up" command are properly removed. Signed-off-by: SammyOina <sammyoina@gmail.com> * Fix proxy address bug in main.go The proxy address was not being set correctly in the main.go file, resulting in incorrect routing of HTTP requests. This commit fixes the bug by correctly setting the proxy address. Additionally, it registers the proxy handler for all incoming requests. Fixes: #123 Signed-off-by: SammyOina <sammyoina@gmail.com> * Refactor main.go to simplify HTTP server setup The previous implementation of the main.go file had unnecessary complexity in setting up the HTTP server. This commit simplifies the code by removing the unnecessary switch statement and consolidating the server setup logic. The main changes include: - Removing the switch statement that handled HTTPS server setup - Consolidating the server setup logic into a single goroutine - Removing the unnecessary goroutine for starting the server These changes make the code more readable and maintainable by reducing unnecessary complexity and improving the overall structure of the code. Signed-off-by: SammyOina <sammyoina@gmail.com> --------- Signed-off-by: SammyOina <sammyoina@gmail.com>
Mainflux
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 (Prometheus and OpenTelemetry)
- 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:
- Docker (version 20.10)
- Docker compose (version 1.29)
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-composeshould 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!
- Take a look at our open issues. The good-first-issue label is specifically for issues that are great for getting started.
- Checkout the contribution guide to learn more about our style and conventions.
- 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
Data Collection for Mainflux
Mainflux is committed to continuously improving its services and ensuring a seamless experience for its users. To achieve this, we collect certain data from your deployments. Rest assured, this data is collected solely for the purpose of enhancing Mainflux and is not used with any malicious intent. The deployment summary can be found on our website.
The collected data includes:
- IP Address - Used for approximate location information on deployments.
- Services Used - To understand which features are popular and prioritize future developments.
- Last Seen Time - To ensure the stability and availability of Mainflux.
- Mainflux Version - To track the software version and deliver relevant updates.
We take your privacy and data security seriously. All data collected is handled in accordance with our stringent privacy policies and industry best practices.
Data collection is on by default and can be disabled by setting the env variable:
MF_SEND_TELEMETRY=false
By utilizing Mainflux, you actively contribute to its improvement. Together, we can build a more robust and efficient IoT platform. Thank you for your trust in Mainflux!