We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having spoken with Adam, we plan to use a well known pattern for config storage.
This follows how AWS's SDK operates. stores a raw API key (in our case, purposely created for CLI operations), in %HOME%/.config/%APPNAME%/%FILENAME%
%HOME%/.config/%APPNAME%/%FILENAME%
$ cat ~/.config/deepgram/config.yaml api_key: accesstoken: 361fa0a8376414ba897a67609476e966d54d1cf1 projectid: ""
The text was updated successfully, but these errors were encountered:
lukeocodes
No branches or pull requests
Having spoken with Adam, we plan to use a well known pattern for config storage.
This follows how AWS's SDK operates. stores a raw API key (in our case, purposely created for CLI operations), in
%HOME%/.config/%APPNAME%/%FILENAME%
The text was updated successfully, but these errors were encountered: