Store GitHub credentials in a configuration file

[sjackman]

I'm running grip --export from the command line, and the result is an HTML file composed of 403 Forbidden. Could a ~/.grip.conf file contain the username and GitHub API token?

See #48 Clarify 403 API "rate limit exceeded" errors in the application

[joeyespo]

Do you mean API token, or user password as used with --pass.

Do you know how to set up an API token?

[joeyespo]

Fixed this with f712f86.

By fixed, I mean that you can add a settings.py file to your ~/.grip directory and settings can be read from there. You can add USERNAME and PASSWORD variables there.

If you really did mean "API token", let's open another issue for that, covering that feature across the entire app (as opposed to just in this new config file). That is, let's have it cover the CLI argument, configuration options, the actual token-sending functionality, and updating the docs. In the meantime, since this settings.py file is just a Python file, you can add code there to prompt for you password instead of storing it there.

Does this help?

[sjackman]

The utility gist has a gist --login feature that works well. Perhaps grip could model its authentication after gist.

https://github.com/defunkt/gist#login

[joeyespo]

I like that. Good find!

Grip does allow you to use OAuth now, but I'll open a new issue for improving the configuration experience like Gist.

Thanks for sharing, @sjackman!