Suggestion: Write a standalone tool that does the code extraction step, so someone can run it on their private repository (or checked-out code) and generate the data dump you need.
This mitigates some of the security issues have with granting access to live repositories, as well as opens your service up to people who have code hosted on anything besides Github or Bitbucket hosted services.
Didn't expect this to blow up today. But security was considered from day 0.
- Each time a poster is generated the repo's code is fetched and destroyed.
- Your auth token is cleared after each session.
- For maximum security use Gists!
You can create a private Gist[0] and add all the files you want into it. After that you can just use the Gist's ssh/https url under the "Embed" menu/dropdown.
This will allow you to specify exact files that get cloned.
Comments
Suggestion: Write a standalone tool that does the code extraction step, so someone can run it on their private repository (or checked-out code) and generate the data dump you need.
This mitigates some of the security issues have with granting access to live repositories, as well as opens your service up to people who have code hosted on anything besides Github or Bitbucket hosted services.
Didn't expect this to blow up today. But security was considered from day 0.
- Each time a poster is generated the repo's code is fetched and destroyed.
- Your auth token is cleared after each session.
- For maximum security use Gists!
You can create a private Gist[0] and add all the files you want into it. After that you can just use the Gist's ssh/https url under the "Embed" menu/dropdown.
This will allow you to specify exact files that get cloned.
[0] https://gist.github.com/