Andy Heydon - Feb 15, 2018:
B) Spin up a CS server as before but don’t open the port to the outside world. Instead use a web front end, for example the example shipped with CS, as the view to the outside world and behind the covers it communicates to the CS server on its port. The shipped example uses PHP which has raw sockets support, but you could use anything and have any number of layers between the user and CS.
In our own situation, we have a number of different input channels (web, mobile app, slack, SMS, messenger) that post input to a nodeJS app, which in turn repackages the text and puts it into a message queue which ultimately gets dequeued and sent to a free CS server.
Super helpful thanks! Your implementation is very much what I am aiming for. I have already created and successfully run a web front-end based on the php template provided for the UI, with a couple of jquery files to interact with the JSON back and forth. I’d like to move to a full PWA and/or multi-channel bot like yours. Do you happen to have a github repo open for inspiration?
From what you say, as long as I have an unused port open, the php script will activate the bot in the server automatically when people land on the bot page. So in theory, as long as my bot works on LocalServer.Bat I don’t need to do anything in the back end, other than having Chatscript in the public.html directory, next to the ui.php and index.php files. Is that right?
Something like:
public.html
-CHATSCRIPT_FOLDER
—-BINARIES
—-LIVEDATA
—-RAWDATA
—-SERVER BATCH FILES
—-TOPIC
-SCRIPTS
-CSS
-ASSETS
-ui.php
-index.php
Is this right?
And thanks Bruce for the headsup re:amazon. Will definitely check it out - you’ve given me a solution if I can’t get my server to work.
Thank you all for your help. Consider me a new, enthusiastic member of the community - I intend to be working professionally with CS for a long time to come. Your help in climbing the early learning curve is profoundly appreciated.