-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NOISSUE - Add docker-compose for MQTT cluster #841
Conversation
Codecov Report
@@ Coverage Diff @@
## master #841 +/- ##
==========================================
+ Coverage 85.53% 85.57% +0.04%
==========================================
Files 72 72
Lines 4708 4708
==========================================
+ Hits 4027 4029 +2
+ Misses 445 443 -2
Partials 236 236
Continue to review full report at Codecov.
|
WIP label removed This PR tries to move as much as possible of mutual Additionally, in
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
site/ | ||
.vscode | ||
|
||
# MQTT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to keep this in its own folder. Monorepo consists of multiple projects, where each has its own .gitignore.
Its much cleaner IMHO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer this centralized overview and one-place tuning. For now our structure is small enough, and sections are well commented.
If really needed let's do this in a separate issue, not to delay this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just fix gitignore
Signed-off-by: Drasko DRASKOVIC <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
Signed-off-by: drasko <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
* Add MQTT cluster configs Signed-off-by: Drasko DRASKOVIC <[email protected]> * Bump worker_connections value in nginx.conf Signed-off-by: drasko <[email protected]> * Revert config.toml Signed-off-by: drasko <[email protected]> * Fix cluster Signed-off-by: drasko <[email protected]> * Move non-ssl server into the same directive Signed-off-by: drasko <[email protected]> * Fix cluster Signed-off-by: drasko <[email protected]> * Remove unnecessary comments Signed-off-by: drasko <[email protected]> * Organize docker-compose and nginx conf files Signed-off-by: drasko <[email protected]> * Correct nginx.conf for mTLS and aux changes Signed-off-by: drasko <[email protected]> * Fix NginX conf trailing slash in proxy_pass Signed-off-by: drasko <[email protected]> * Fix path for MQTT Signed-off-by: drasko <[email protected]> * Fix minorstuff in gitignore and comments Signed-off-by: drasko <[email protected]>
Pull request title should be
MF-XXX - description
orNOISSUE - description
where XXX is ID of issue that this PR relate to.Please review the CONTRIBUTING.md file for detailed contributing guidelines.
What does this do?
Introduces docker-compose files for MQTT cluster. Also, modifies
nginx.conf
to improve performance.Which issue(s) does this PR fix/relate to?
Put here
Resolves #XXX
to auto-close the issue that your PR fixes (if such)List any changes that modify/break current functionality
nginx.conf
files have been changed, and this demands testingHave you included tests for your changes?
Did you document any new/modified functionality?
Notes