-
Notifications
You must be signed in to change notification settings - Fork 859
Secrets File
archpdx edited this page Nov 18, 2021
·
4 revisions
In order to sucessfully run npm run wikidata
, you first have to add a secrets.json
file in the project root (same folder as package.json
and README.md
etc.) - here is the format of the secrets file:
{
"twitter": [
{
"twitter_consumer_key": "••••••••••",
"twitter_consumer_secret": "••••••••••",
"twitter_access_token_key": "••••••••••",
"twitter_access_token_secret": "••••••••••"
},
… + a few more of these to avoid the rate limit …
],
"wikibase": {
"username": "bhousel",
"password": "••••••••••"
}
}
If you don't know how to get Twitter app keys, there's a guide on how to do so below. wikibase
is just the username and password for your Wikidata account. This file will not be added to the repo on your next commit as the file is in .gitignore
- Sign up for a Twitter dev account
- Add a standalone app
- Open the settings for the app and click on
Keys and tokens
- Click on
Generate
under Access Token and Secret - make sure to save these to your secrets file as you won't be able to view these again without regenerating them - Make as many apps as you want to avoid the rate limit. Twitter limits you to creating 10 apps with a free account (3 apps per day), which is fine for running
npm run wikidata
.
Contributing to the index
- Feature Files (geofences)
- Using Overpass Turbo
- Config Files
- Property Reference
- Technical Details
Information for developers using the name-suggestion-index in another project.
Information for maintainers, including how to clone and build the project.