I am just thinking of the next aspect of the cli. Once a brand new user npm installs twindle, we should be able to do all the initialization for twindle to the user's home folder (on all OSes) and whatever configuration needs to be stored centrally there in some kind of env file.
Also there would need to be some guided steps. The user should be guided through
how to get the bearer token from twitter developers
how to setup the kindle to receive email (and associated configuration)
how to setup email credentials
Once the user has performed these steps, then we would have all the config ready for usage.
Ideally we may expose just the -i tweetId flag for easiest UX.
This would require some more thoughts to refine it, before we proceed with implementation.
I am just thinking of the next aspect of the cli. Once a brand new user npm installs twindle, we should be able to do all the initialization for twindle to the user's home folder (on all OSes) and whatever configuration needs to be stored centrally there in some kind of env file.
Also there would need to be some guided steps. The user should be guided through
Once the user has performed these steps, then we would have all the config ready for usage. Ideally we may expose just the
-i tweetId
flag for easiest UX.This would require some more thoughts to refine it, before we proceed with implementation.