Skip to content
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

Improve configuration option documentation #274

Closed
ralight opened this issue Sep 22, 2016 · 4 comments
Closed

Improve configuration option documentation #274

ralight opened this issue Sep 22, 2016 · 4 comments

Comments

@ralight
Copy link
Contributor

ralight commented Sep 22, 2016

See http:https://dev.eclipse.org/mhonarc/lists/mosquitto-dev/msg01266.html

@Asoul
Copy link

Asoul commented Oct 24, 2016

+1
I have no idea how the configuration file is parsing, there are too many same keyword, sometimes search an keyword will go to the different listener, and user may misplaced the config

Maybe some YAML file or more structural file is better

@ralight
Copy link
Contributor Author

ralight commented Oct 24, 2016

You're proposing a different issue here. This issue is around documentation, not around changing the file format which is something that will now have a huge impact.

@M-ax-G
Copy link

M-ax-G commented Jan 18, 2017

Agree with the initial message (referenced in the first post)... I thought I could have a listener on 1883 for the local network (all default config, basically nothing), and another listening on 8883 accessible from the Internet requiring authentication... and also discovered that allow_anonymous is global...

@ralight ralight added this to the 1.6.5 milestone Sep 4, 2019
@ralight
Copy link
Contributor Author

ralight commented Sep 4, 2019

All listener options are now labelled as global or per-listener, and will be in 1.6.5.

@ralight ralight closed this as completed Sep 4, 2019
ralight added a commit that referenced this issue Sep 4, 2019
ralight added a commit that referenced this issue Sep 18, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants