[How-to guide]: Why do I get a warning that no responses can be found?

[garrytrinder]

We should add a guide to the common problems section to highlight why this is and how to resolve it.

[waldekmastykarz]

Alternatively, we should consider supporting something like an ~appfolder token that points to the folder where the application is located so that we can point to the empty file we ship with the Developer Proxy rather than looking it up in the current working directory.

@gavinbarron @sebastienlevert what do you think? The question is that right now, when you start the Developer Proxy from a folder different than the installation folder, you're getting a warning that we can't find the responses.json file to load mocks. It might be odd that the app feels "broken" after you've just downloaded it and run it.

[sebastienlevert]

I like the use of the AppFolder instead of the extracted directory. Makes it ways easier. How is that affecting multiple "versions" of the proxy running in multiple folders, though?

[waldekmastykarz]

When specifying file path you could choose to pass either an absolute path, relative to the current working folder, or ~AppFolder which is the default that we'd ship to avoid broken default behavior. Since it's a config setting you can choose how you want the Developer Proxy to work.

Right now we support only the relative path. Absolute and ~AppFolder would be enhancements for future releases.