hawm encountered an issue when setting up a development environment using Docker as a DiscourseConnect provider. The issue causes an error when the consumer redirects to Discourse. hawm suspects it’s an Ember CLI problem and shares their development environment installation steps.
Simon reports experiencing the same issue but hasn’t had a chance to investigate further. hawm temporarily resolves the issue by disabling Ember CLI, further suggesting that the problem is related to Ember CLI’s handling of external redirects.
merefield offers insight from their non-Docker setup, where they successfully redirected calls to port 4200 using nginx. They suggest a similar approach might work for Docker by mapping ports to send incoming calls to 4200.
However, hawm reports that while Ember CLI is now working, the issue persists with the DiscourseConnect provider. merefield acknowledges that their previous suggestion only solved part of the problem and that there’s an additional level of complexity to resolve.
I have run into the same issue myself, but haven’t spent time yet on sorting it out. I’ll do that early this week and report what I find here, unless someone solves the issue for you before then.
FYI not Docker but I’m using Ember CLI with a non-docker dev setup in the cloud
All I had to do was redirect calls to port 4200 (in my case using nginx) which connects to the ember server which in turn connects to the Rails server on 3000 (no change there)
This suggests for docker you probably just need to run the container with a port mapping to send incoming calls to 4200 to get it to work with ember CLI?