-
Notifications
You must be signed in to change notification settings - Fork 25
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
Failure to auto-detect nested CMS installation? #22
Comments
Debugging has proved that fetching CMS meta works just fine with nested CMS. Will create a new issue if I can't figure it out why I keep a 404 response. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My ContentaCMS is nested (localhost:MAMP-PORT/contenta/web), installed via contenta_jsonapi_project. When writing ContentaJS local config, 'cms.host' requires a complete path to the ContentaCMS to get any type of connection to the node proxy, otherwise connections are refused.
While the app is accepting connections, requests sent to the node proxy api (localhost:NODE-PORT/api) get a 404 response in HTML:
...<pre>Cannot GET /api</pre>...
Direct requests to ContentaCMS API work perfectly.
I've started to go through the built code, but haven't had much luck in finding a solution.
Suggestions?
The text was updated successfully, but these errors were encountered: