Twitter keys ENV variables
See original GitHub issueThe ones that are currently in use look terribly generic and I can see them causing issues in the future. Would it make sense to make them scoped like all the configuration ones?
Eg.
CONSUMER_KEY='...'
CONSUMER_SECRET='...'
ACCESS_TOKEN='...'
ACCESS_TOKEN_SECRET='...'
would be
TTC_CONSUMER_KEY='...'
TTC_CONSUMER_SECRET='...'
TTC_ACCESS_TOKEN='...'
TTC_ACCESS_TOKEN_SECRET='...'
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Authentication - Regenerate API keys and tokens
Use server environment variables. By storing API keys in environment variables, you keep them out of your code and version control. This also...
Read more >Manage follows quick start guide | Docs - Twitter Developer
These variables will automatically be pulled into the request's authorization tab if you've done this correctly. Step three: Specify who is going to...
Read more >Securing Keys and Access Tokens | Docs - Twitter Developer
Use server environment variables. By storing API keys in environment variables, you keep them out of your code and version control.
Read more >Step-by-step guide to making your first request to the Twitter ...
This is a detailed walkthrough of all the basic steps for getting started with Twitter API v2 from sign up to endpoint request....
Read more >Getting started with Postman | Docs | Twitter Developer Platform
Step one: Add one of the Twitter Postman collections to your account · Step two: Add your keys and tokens as environmental variables...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I did not managed to test it on FreeBSD, recent Ubuntu/CentOS seems not have this problem anymore.
Anyway, env variables are terrible - they leak everywhere - cronjobs, child shellscripts, etc. Also you cannot change them without restarting process. but anyway, this is out of scope of this ticket.
Thanks @notwaldorf I’ll check it out