base url config
I want to differentiate multiple answer communities through nginx by using a domain name and URL
To Reproduce
Steps to reproduce the behavior: I changed the REACT.APP_BASE.URL through the. env.production under the UI package, but after the modification, it kept redirecting 50x.
Expected behavior
Screenshots
May I ask the author, what else do I need to configure a secondary domain name,Thank you
Platform
- Device: [Desktop]
- OS: [windows]
- Browser and version: [Chrome]
- Version: [e.g. v1.3.5]
You can refer to this document: https://answer.apache.org/docs/deploy-subdirectory.
If you still have problems after trying it, you can continue to give feedback.
Run the command Initialize the project, note that you need to add your base_url (http://localhost:80/{base_url}/install/) to the access path here to see if the configuration is successful.INSTALL_PORT=80 . /answer init -C . /answer-data/.Is there a tutorial on how to add it to the access path when I initialize the third step? INSTALL_PORT=9080 REACT_APP_BASE_URL_PATH=/foo ./answer init -C ./answer-data/?thank you
You can look at it in conjunction with this document: https://answer.apache.org/docs/installation.
Normally, after the initialization command completes, the access address should be localhost:80/install, but if you change the value of base_url, the access address should be http://localhost:80/base_url/install, all you need to do here is manually splice in the access address, the actual configuration should be done here
If my base_URL is/foo, what command should I use to initialize it?
INSTALL_PORT=80 . /answer init -C . /answer-data/
Don't you need to add base_URL here? Can I access it directly through localhost/foo/install after initialization?
Don't you need to add base_URL here?
No, it's just a startup command. base_url is for injecting paths when building static resources in the front end.
Can I access it directly through localhost/foo/install after initialization?
Yes!
There was an issue with the reverse proxy
Problem:no data
Nginx
Info
code config
May I ask what the problem is and if there are any further modifications needed.Thank you
From your Nginx configuration, you don't have proxy api related configuration, so api_url should be ingested as default, you can also look at the network request from the console, and then manually remove the api_url prefix to manually request for testing.
same issue here