Skip to content

Commit

Permalink
new release for prep replies
Browse files Browse the repository at this point in the history
  • Loading branch information
abrahamq committed Aug 22, 2018
1 parent d3b9d3c commit 3cc7e3e
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 1 deletion.
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,6 @@ Deployment version:

### v0.1.1
- Allow multiple card decks

### v0.1.2
- Prep cards in reply
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ Save a copy of sample.env as .env in local directory with appropriate credential
Configuration variables are as follows:
* `API_GW_WEBHOOK` - the API GW address for the webhook endpoint (e.g. https://chatbots.riskmap.us/facebook/webhook). Currently this is unused by functions and is for reference
* `CARDS_API` - the endpoint to get new report cards
* `CARDS_DECK` - which cards decks are deployed on this instance. Subset of 'flood,prep'.
* `CARDS_API_KEY` - the api key for the cards endpoint
* `CARDS_URL` - the URL for card resources as sent to the client
* `DEFAULT_INSTANCE_REGION_CODE` - in case a report is submitted outside a city, what city should the code fallback on
Expand All @@ -34,6 +35,7 @@ Configuration variables are as follows:
* `FACEBOOK_VALIDATION_TOKEN` - a random string that is a shared secret between Facebook and this software (e.g. a [UUID](https://duckduckgo.com/?q=!guid))
* `MAP_URL` - the risk map URL
* `NETWORK_NAME` - 'facebook' for CogniCity logging
* `PREP_URL` - the prep card url (e.g. https://cards-dev.riskmap.in/prep/)

### Facebook Configuration
- To subscribe to the get started button, make sure the app is subscrived to `messaging_postbacks` as set in the Messenger -> Settings -> Webhooks -> Edit events config page in developers.facebook.com
Expand All @@ -46,4 +48,4 @@ run `npm run test`
1. Update CHANGELOG.md
2. Commit all changes
3. Tag release in Git and create release in GitHub
4. On the dev branch increment the version number, new development takes place in the new version
4. On the dev branch increment the version number, new development takes place in the new version

0 comments on commit 3cc7e3e

Please sign in to comment.