We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think we could start the hot reload server with an env var (or even start on different ports in the proc file!) and show this off.
By Proxy first or last, that will determine if the callbacks in server.js or the rails server handle the API calls.
The text was updated successfully, but these errors were encountered:
@necronet Would you be able to try this out in a fork?
Sorry, something went wrong.
I have a similar setup with using contenBase and seems webpack setup the proxy to point to the proper endpoints I'll do an sample on this!
contenBase
@necronet Please create a fork and maybe we can bring this in, and if it's super cool, @robwise will put in our generator.
Closing this as we'll soon be changing around a few things which will address this issue.
No branches or pull requests
I think we could start the hot reload server with an env var (or even start on different ports in the proc file!) and show this off.
By Proxy first or last, that will determine if the callbacks in server.js or the rails server handle the API calls.
The text was updated successfully, but these errors were encountered: