-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy path.env
57 lines (49 loc) · 2.3 KB
/
.env
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
#
# Store your bot settings in env variables below
# or specify your settings on the command line
#
# - note that this file is versionned by default
# DO NOT PUT SECRETS IF YOU'RE PUSHING THE CODE TO EXTERNAL REPOS
# as strangers would see your .env values
#
# - you can reference these variables from your code with process.env.SECRET for example
#
# - note that ".env" is formatted like a shell file, so you may (depending on your platform) need to add double quotes if strings contains spaces
#
# Uncomment if you wish to statically set a Webex Teams API access token
# - if you do so, make sure not to version that file in a public repo
# - if running the code from a private machine, setting secrets on the command line is recommended
#ACCESS_TOKEN=
# Secret used to generate an HMAC-SHA1 for each payload submitted to your bot
# Optional but highly recommended to use a Secret when going to production
#SECRET="Not That Secret"
# Internet facing URL where your bot can be reached
# note that Botkit automatically appends a relative path ("/ciscospark/receive")
# uncomment one of the examples below or simply add the public route to your bot
#PUBLIC_URL=https://myapp.appspot.com
#PUBLIC_URL=https://your-app.herokuapp.com
#PUBLIC_URL=https://sharp-stove.glitch.me
# Name used to create the webhook to register your bot against Webex cloud platform
# Defaults to 'built with BotKit (development)'
#
# WARNING: if you explicitely override this value,
# - Botkit will automatically create a new webHook with the ACCESS_TOKEN above
# - BUT Botkit will not delete the previously created webhook entry
# - YOU will need to take this action manually
# HERE'S HOW
# - manually list your bot webhooks via Postman or the Webex for Developers documentation
# /!\ make sure to use your bot's access token
# https://developer.webex.com/endpoint-webhooks-get.html
# - identify the previously registered webhook identifier and delete it
# https://developer.webex.com/endpoint-webhooks-webhookId-delete.html
#WEBHOOK_NAME="built with BotKit (development)"
# Local port where your bot will be started
# defaults to 3000
#PORT=3000
# Node Environment
# defaults to development
NODE_ENV=production
# Healthcheck route, defaults to "/"
HEALTHCHECK_ROUTE="/"
# Metadata route, defaults to "/botcommons"
BOTCOMMONS_ROUTE="/botcommons"