Skip to content
New issue

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

Use viper to read api keys from config file instead of taking at compile time #3

Closed
mattgen88 opened this issue Apr 21, 2018 · 1 comment

Comments

@mattgen88
Copy link

Use viper to read api keys from config file instead of taking at compile time
if no config file exists, scrobble should prompt user for them or direct user to set them, possibly creating skeleton config file.
Scrobble could use the same mechanism to also take them from environment.

@mattgen88
Copy link
Author

Scratch that, they need to be stored in the released binary. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant