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
Can't get it to work #5
Comments
I've just download again the npm module and try it and it is working on my side, with node v0.12.0 and npm 2.5.1. Can you provide the raml you are using just for checking and the node version? |
i'm struggling to get it running as well and I have the same issue. Just using your exampleApi.raml. Always get 404 error when i put in localhost:3000/songs in web browser. seems the raml file is not being loaded. i can put in $ raml-server somefake.raml which is a raml file that does not exist on my machine and it still starts up and gets the same errors. running node v0.12.2 and npm 2.7.4 |
Facing the same issue.
Have tried with provided example RAML:
|
as PR was merged, it should work now :) |
Hi, I have the following problem, when I run raml-server using the command I'm using node version 4.3.1 Thank's |
Hi @rac021 sorry for the late response, will take this one ASAP :) |
I installed it locally (w/o the -g option).
Then run it as: raml-server path-to-raml-file/api.raml
Then hitting the top level resources at http://localhost:3000/top-level-resources always returns empty object {}, while the server logs reports 404. I made sure that my raml file has no include (only a single file), and has a schema defined for the response.
I tried with your exampleApi.raml, and hit http://localhost:3000/songs, got same result (404). In any case, if I hit the base url http://localhost:3000/, a successful page is returned with the first sentence "Congrats! You're successfully running JSON Server".
Any idea?
Thanks.
The text was updated successfully, but these errors were encountered: