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

Crawler configuration: add 'Config Parameters' reference in documentation #1862

Closed
fbaligand opened this issue Oct 6, 2018 · 11 comments
Closed
Labels

Comments

@fbaligand
Copy link

There are lots of 'Config Parameters' available to configure a crawler.
But unfortunately, there are currently undocumented.

This would be great to list all possible crawler 'Config Parameters' in official documentation.
Or maybe reference a file on github listing all possible 'Config Parameters'.

@fbaligand
Copy link
Author

Hi @marevol,

In my mind, this is not a question, but more a documentation enhancement request.

@fbaligand
Copy link
Author

That said, if you have some location (github file, blog, any link) where all Config Parameters (or at least the major part) are referenced, I would be happy to know it !

@zackhorvath
Copy link

I'd be really happy to know too!

@Anders-Bergqvist
Copy link

Me too!

@cityofaikensc
Copy link

I too would love to see this as I am finding it difficult to understand the true power of this application without knowing all the config parameters.

@marevol
Copy link
Contributor

marevol commented Feb 6, 2019

#1686

@marevol marevol closed this as completed Feb 6, 2019
@fbaligand
Copy link
Author

Hi @marevol,

If I understand well, this issue is closed because it is a duplicate of #1686 ?

@marevol
Copy link
Contributor

marevol commented Feb 7, 2019

This issue is a documentation work for us, so I closed it as duplicate.
Fess is an open source product.
Any contributions including documentations are welcome!

@fbaligand
Copy link
Author

As an open source contributor, I fully understand your purpose!
But it’s complicated to document hidden features that you don’t even know.
If I open this issue, it is first because I guess there are several useful config parameters, but I don’t know about them.
And honestly, this is quite frustrating.

@jamiejackson
Copy link

@marevol this is like asking us to read your mind then document what's in there.

It can be hard to reverse-engineer intent from source code. I understand not having time to make documentation pretty or get the wording perfect, but at least give us some scraps to work with that we can then turn into PRs. Even an ugly list of params, written here, would be fine.

Otherwise:

  • 99% of potential implementers would not know about configuration options
  • The remaining 1% who discover that there are hidden options would then play a guessing game as to what the options do and how to use them

@stratocentric
Copy link

Has anyone found or started a resource for this? Suggested topics:

FESS

  • kubernetes installation for Digital Ocean
  • configuring search
  • connecting to various api services like rapidapi
  • distributed data resources for JSON

I will host a wiki or similar for this if anyone is interested... also add the topics you want to cover.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants