summaryrefslogtreecommitdiff
path: root/doc/TWITTER_FEED.md
diff options
context:
space:
mode:
authorMarie <ml.kochsiek@fu-berlin.de>2016-09-22 19:34:16 +0200
committerGitHub <noreply@github.com>2016-09-22 19:34:16 +0200
commit873ba38715bb0e08f39a1effd64a26e9d05af78b (patch)
tree7a1472480072f20ccd19b22f1b09b0259efaeff9 /doc/TWITTER_FEED.md
parent22478d315af3590d2a344eb1aa8cf2aec0730506 (diff)
parentd44fc9292637ed6d1a4a7e04883e8b3b88dc3c15 (diff)
Merge pull request #15 from LoadToCode/thea
errorhandling and small changes
Diffstat (limited to 'doc/TWITTER_FEED.md')
-rw-r--r--doc/TWITTER_FEED.md19
1 files changed, 18 insertions, 1 deletions
diff --git a/doc/TWITTER_FEED.md b/doc/TWITTER_FEED.md
index dd3954c..94de8c1 100644
--- a/doc/TWITTER_FEED.md
+++ b/doc/TWITTER_FEED.md
@@ -19,12 +19,29 @@ LEAP web app (as part of the main view).
* Activate the feature within your local LEAP Web Application
* If not already existing create a secrets-file in /config with the name secrets.yml (`/config/secrets.yml`)
* Secrets-file should contain the following, make sure its in YAML: {"development"=> {"twitter"=>{"enabled"=>false, "twitter_handle"=>"", "bearer_token"=>"", "twitter_picture"=>nil}}, "test"=>{"twitter"=>{"enabled"=>false, "twitter_handle"=>"", "bearer_token"=>"", "twitter_picture"=>nil}}}
+```
+development:
+ twitter:
+ enabled: false # set to true for usage
+ twitter_handle: XXXXX #put your twitter handle here
+ bearer_token: XXXXX #put your bearer token here
+test:
+ twitter:
+ enabled: false # set to true for usage
+ twitter_handle: XXXXX #put your twitter handle here
+ bearer_token: XXXXX #put your bearer token here
+production:
+ twitter:
+ enabled: false # set to true for usage
+ twitter_handle: XXXXX #put your twitter handle here
+ bearer_token: XXXXX #put your bearer token here
+```
* To have your bearer token created, run script in terminal being in the file of leap_web: `script/generate_bearer_token`
* To have the script run properly you have to add before running: `--key your_consumerkey --secret your_consumersecret`
* Add also `--projectroot your_projectroot --twitterhandle your_twitterhandle` as well to not have manually put the data in your secrets-file
* The full command looks like this: `script/generate_bearer_token --key your_consumerkey --secret your_consumersecret --projectroot your_projectroot --twitterhandle your_twitterhandle`
* If you didn't give all your information to the script, had a typo or want to change anything else, please do so by finding the secrets-file at `/config/secrets.yml`
- * Make sure that the correct twitterhandle and bearer-token is included
+ * Make sure that the correct twitterhandle and bearer-token is included. The twitter-account you want to have shown (the twitterhandle) is a public account!
* Deactivate your bearer token
* To deactivate your generated bearer token you can run script/invalidate_bearer_token