Publishing as gist about rcharts

[ramnathv]

Here is some info from the ruby implementation jist. So one way I can handle this situation is to do the following the first time get_token is run.

1. ask user for username and password.
2. use it to fetch a token for the gist scope.
3. save the token in ~/.rCharts
4. print a message to the user about the save and how to revoke access

The only thing left to think is (3), a location to save the token. Maybe .Rprofile? I need to brush up a bit on how R starts up.

---

If you want to associate your gists with your github account, you need to login
with jist. It doesn't store your username and password, it just uses them to get
an OAuth2 token (with the "gist" permission).

jist --login
Obtaining OAuth2 access_token from github.
Github username: ConradIrwin
Github password:
Success! https://github.com/settings/applications

This token is stored in ~/.jist and used for all future gisting. If you need to
you can revoke it from https://github.com/settings/applications, or just delete the
file.

After you've done this, you can still upload gists anonymously with -a.

---

[ramnathv]

Another location where the token could be saved is the package directory (which most likely the user has write access to). The one advantage with this approach is cross-platform support. The disadvantage is that the token gets overwritten when a new version of the package is installed.

[ramnathv]

While I am on this, I should add the ability to publish anonymously too. It could be a simple flag to the publish function that can do the trick

• add ability to publish gist anonymously.
• save token generated and use it across sessions.

[timelyportfolio]

think it is something wrong with my local instance, but I'm now getting Error: Forbidden when I try to publish to gist. Any ideas?

[ramnathv]

Try setting your username and password using

options(github.user = 'username', 'github.password' = 'password')

and try. I will be rewriting the publish function to make use of basic authorization rather than OAuth, which is the case currently. Basic authorization is easier as it only requires a username and password and no token fetching, which is how the publish function works currently.

[timelyportfolio]

still does not work. The error comes in the get_token() function. Any way to delete the token?

[ramnathv]

I am getting an error too. Just trying get_token(username, password) is giving me an error. Let me see if I can push basic authorization quickly.

[ramnathv]

Just pushed to github replacing oauth with basic auth. Try again and let me know if it works.

[timelyportfolio]

works great as shown and closed in #42

[ramnathv]

Using basic auth solves the issue for now, since no more token issuing occurs. There is still the problem of using readline for getting username and password, but that should be easy to fix since the options alternative always exists.