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.

Sign up for GitHub

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

Jump to bottom

To do #1

Open
jonathanong opened this issue Jan 14, 2014 · 3 comments
Open

To do #1

jonathanong opened this issue Jan 14, 2014 · 3 comments

Comments

@jonathanong
Copy link
Contributor

Required:

  • tests for proxy
  • tests for auth
  • tests for retries
  • tests for netrc
  • tests for redirects
  • tests for remote server error handling and timeouts

Nice to Have:

  • additional remotes
  • check if a remote is down, then skip using that remote. useful if the registry is ever down
@sankargorthi
Copy link
Member

  1. What support will be provided for corporate git repositories?
  2. What if the repository server doesn't support raw URLs (Gitlab)?

@jonathanong
Copy link
Contributor Author

What do you mean by corporate git repositories? Like github enterprise?

Yeah, getting files on by one is a pain in the ass. Easier to have the proxy filter the files of the repo then send only what's necessary

@sankargorthi
Copy link
Member

We use Gitlab installed on a local server (local to the VPN).

Looking into the documentation to find solutions for proxy filters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonathanong @sankargorthi