Hej,
On 4. Juli 2016 at 20:00:26, 123Dev ([email protected]) wrote: > First and foremost, that statement was not meant as a knock on Graylog > documentation, in fact I'm impressed how fast and frequent the docs are > updated and kept current. thank you for this, i will forward it to the dev team! > Given all the configuration / distribution varieties, it is a > understandably impossible to have flawless documentation. > Seriously you guys have been amazing with the development and documentation > Graylog. we try to improve not only the product, the surroundings are important as well. > Having said that, we ourselves still struggle getting the REST API part of > the setup working correctly, even after experimenting lots of configuration > options and reading many forum / issue tickets. that is why we will do a change here in the next release. if everything is working as we had planed the next version should easy that up. — spoiler - all components use the same port and routing is done by url - spoiler - after this is ready we will work on the documentation and try to cover aws production setups too. but it would be helpful if you submit your findings as issues or even better as pull request for the documentation https://github.com/Graylog2/documentation thank you jan -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/CAGm-bLbMJkumdexmseo1jpVZy__nCQ-gC9s88h8UjBBNB2OEdA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
