Re: [racket-dev] Using private github repositories as package sources?

2016-06-20 Thread Alexis King
Alright, I’ve opened a pull request that adds support for authentication to net/git-checkout, which appears to be able to successfully clone private GitHub repositories. Presumably, adjusting the package system to use this information is not terribly technical difficult, but I’m finding myself fair

Re: [racket-dev] Using private github repositories as package sources?

2016-06-17 Thread Matthew Flatt
Accessing private GitHub repos via HTTPS URLs is a matter of adding a Authorization: Basic header to the request sent by `net/git-checkout`, where "password" is a GitHub personal access token. (I temporarily added a hardwired line in `http-request-headers` in `net/git-checkout` to check that it

[racket-dev] Using private github repositories as package sources?

2016-06-17 Thread Alexis King
I have been looking for a way to use Racket at work, and we’ve found a couple places where it might be useful for documentation or tooling. As part of this, it would be very nice to keep our source code private, but it would still be helpful to make use of the package manager to handle dependency r