edu / BeuthBot_WS17 · Commits

Commit a0300411576baf929dcadd35c4b867683a321a7c

Authored by hausdoerfer
1 parent 479ced06
build: skipped

added description for set webhook

Inline Side-by-side
Showing 1 changed file with 3 additions and 1 deletions
README.md
  View file @a030041
... ... @@ -85,7 +85,7 @@ After the application has started the following two endpoints of the server are
85 85 - WildFly Server Manager: <http://localhost:9990/>
86 86 - Rasa: <http://localhost:5000/parse?q=Hello>
87 87  
88   -It is possible to use a Postman Collection to test the configured endpoints for Telegram and Facebook. The `docu/postman/` directory includes a Postman collection containing corresponding endpoints. The JSON file `beuth-bot.json` can be imported into Postman. If changes are made to the Postman collection, the service of the JSON file should be increased accordingly.
  88 +It is possible to use a Postman Collection to test the configured endpoints for Telegram and Facebook. The `docu/postman/` directory includes a Postman Collection containing corresponding endpoints. The JSON file `beuth-bot.json` can be imported into Postman. If changes are made to the Postman Collection, the service of the JSON file should be increased accordingly.
89 89  
90 90 In addition it is also possible to set up your own bot for example, in Telegram and test it with the local server. For this however a local tunnel must be set up to make the application visible to the outside. For details see the section [Local tunnel](#Local tunnel).
91 91  
... ... @@ -271,6 +271,8 @@ In addition a folder with the project name `&lt;projectname&gt;` has to be created on
271 271 mkdir ~/<projectname>
272 272 ```
273 273  
  274 +If the URL of the BeutBots API changes, the variable `WEB_URL` in the` beuthbot.proterties` has to be adjusted. In addition the call of `setWebhook` methods for Facebook and Telegram is necessary. The corresponding endpoints can be found in the Postman Collection.
  275 +
274 276 ### 2. Use in a local development environment
275 277  
276 278 This step sets up a reference to the server on which the application is deployed. For this the following command must be executed. The placeholder `<user>` has to be replaced by the matching SSH user and the project `<projectname>` that has been set up on the server.
... ...