document connecting to an NLU only server #7475
Conversation
|
@melindaloubser1 did you check that it still behaves as expected? |
|
i'm also not sure this belongs in the NLU only section 🤔 you'd usually use that if you're running the dialogue manager and NLU separately |
|
Yes, it does behave as expected. I wasn't really sure where to put it since there isn't an "endpoints" page specifically - should it go under the http api page? |
|
@erohmensing i feel like you probably know better where it should go? |
docs/docs/nlu-only.mdx
Outdated
| The dialogue management server should serve a model that does not include an NLU model. | ||
| To obtain a dialogue management only model, train a model with `rasa train core` or use | ||
| `rasa train` but exclude all NLU data. |
There was a problem hiding this comment.
I would put this part at the top where we introduce the "dialogue management only server", or create another short header explaining what that is and how to spin one up
|
Moved it to its own page under API |
Co-authored-by: Ella Rohm-Ensing <erohmensing@gmail.com>
indam23
requested review from
a team and
chdorner
and removed request for
a team
|
@melindaloubser1 can this be merged? |
|
In general yes, but looks like there's a validation error that prevented auto-merging; I'll look into it |
Proposed changes:
Status (please check what you already did):
black(please check Readme for instructions)