You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2022. It is now read-only.
I expected the interface were looking for /nlp/api/settings and /nlp/api/agent resources, where resource really are. Looks like SETTINGS_URL and API_URL are ignored.
The text was updated successfully, but these errors were encountered:
To reflect changes made in client/.env you need to rebuild as frontend don't work with env variables by default. This generates build and this content is served in public folder on the root.
Something like that:
Modify client/.env
npm run build
cd ../
rm -rf public
mv client/build public
Thank you @ericzon for reply. That's what I did. I rebuilt using parameters I've described in step 3. Looks like this was not enough because /api/settings & /api/agent weren't rewritten although are now served at /nlp/api/settings & /nlp/api/agent.
/nlp is my proxy mount point.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While loading the web interface I got a 404 error "something went wrong" because browser can't load
/api/settings
neither/api/agent
resources.Settings are missing and Agents can't be loaded because resorces are served at:
/nlp/api/settings
and/nlp/api/agent
File swagger2.json is correctly loaded from:
/nlp/swagger2.json
Steps to reproduce the behavior:
I expected the interface were looking for
/nlp/api/settings
and/nlp/api/agent
resources, where resource really are. Looks like SETTINGS_URL and API_URL are ignored.The text was updated successfully, but these errors were encountered: