Closed langel closed 8 years ago
Figured this out. W/o using docker you can set the local http server IP address to "localhost" or 127.0.0.1, but when it's inside docker it wants 0.0.0.0 Fuuuuuuuu Also, the exec curl command was missing a space between the post data and the domain URL on the site side of things. Daaaarrrrrr
This is just a note to myself. I swear when I moved the production bot to AWS using a docker container that the http server was accessible. I could have imagined it. I played around with opening ports in the amazon EC2 client, but still blocked. This is important; it lets the site talk to the bot directly which is a feature of the old bot.