Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Clarification of baseURL and publicPath settings in apiconfig.json #4

kamalgill opened this Issue Aug 11, 2011 · 2 comments


None yet
2 participants

kamalgill commented Aug 11, 2011

Does the baseURL require a host name rather than a URL prefix?

Downloaded I/O Docs on August 10, 2011 from GitHub and noticed the apiconfig.json settings for baseURL expects a host name (e.g. example.com) rather than a URL prefix (e.g. http://example.com/api), with the publicPath expected to be the full relative path to the api (eg. /sampleAPI/v1) rather than a simple version identifier.

To clarify, if the API URL is at 'http://example.com/sampleAPI/v1', the baseURL appears to expect 'example.com' while the the publicPath should be '/sampleAPI/v1'.


mansilladev commented Aug 12, 2011

Hello. Originally, we had baseURL accepting a full URL; however, we decided to separate the URI scheme (e.g. http:// https://) and make it a hostname only, and move the scheme into a field named protocol. So to your example:

baseURL => "example.com"
protocol => "http"
publicPath => "/sampleAPI/v1"


mansilladev commented Aug 13, 2011

Thanks - merged pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment