-
Notifications
You must be signed in to change notification settings - Fork 23
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
Have a session relevance evaluator #69
Comments
Can now run root server in a pair of docker containers (1 x BES , 1 x DB2) Anyone think this can be incorporated into the running evaluation engine ? |
@briangreenery -- what do you thing about this one ? I can probably get a few folks looking at it and we can leverage the bfdocker stuff to do it. We could push the session relevance to a web reports? Very easy to populate a db with data using besagent containers. The besserver components are happy in containers. |
Sure, that would be great. |
The current public URL for the current evaluator is here: https://developer.bigfix.com/relevance/evaluate/ The code is here: https://github.com/bigfix/developer.bigfix.com/tree/master/site/pages/relevance/evaluate |
It would be pretty cool to have a textbox on the front page of https://developer.bigfix.com/ that would attempt a session relevance evaluation, a regular relevance evaluation, and a search of the site for whatever was entered. Related: #65 (it would be nice if this capability was more promenent.) |
We should have both a client relevance evaluator - the current one - and one for session relevance.
Thinking the backend for the session relevance evaluator could be a server in a docker container with a few computers added.
The text was updated successfully, but these errors were encountered: