Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Installing a Skeleton Behind a Proxy #1701

Open
procload opened this issue Apr 26, 2017 · 4 comments
Open

Installing a Skeleton Behind a Proxy #1701

procload opened this issue Apr 26, 2017 · 4 comments
Labels

Comments

@procload
Copy link

Description

I'm having issues installing a new Brunch instance with a skeleton because I am behind a proxy. I would like to install the https:// version of the repo instead of the ssh (git://github.com) version of each skeleton. Is there a way to specify the https:// to be cloned instead of the git://github.com when setting up a new project?

Expected behavior

I should be able to run brunch new -s es6 and have it create a new instance of brunch without errors.

Actual behavior

After running brunch new -s es6 I receive the following output because I am behind a proxy:

10:23:07 - log: Cloning git repo "git://github.com/brunch/with-es6.git" to "/Users/r880912/.brunch/skeletons/9152c4186024c8cef4830ecf8bc55c7c86af99d3"...
(node:78593) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Git clone error: Error: Command failed: git clone git://github.com/brunch/with-es6.git "/Users/r880912/.brunch/skeletons/9152c4186024c8cef4830ecf8bc55c7c86af99d3"
Cloning into '/Users/r880912/.brunch/skeletons/9152c4186024c8cef4830ecf8bc55c7c86af99d3'...
fatal: unable to connect to github.com:
github.com[0: 192.30.253.112]: errno=Connection refused
github.com[1: 192.30.253.113]: errno=Connection refused


(node:78593) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Environment

  1. Brunch: 2.10.9
  2. Node.js: 7.7.3
  3. NPM: 4.1.2
  4. Operating system: macOS Sierra
@shvaikalesh
Copy link
Contributor

Hey @procload, thanks for posting this!

There is no way to configure this and I would rather not expose it. I will research git: vs https: maybe we can just change protocol to https: and it will work for everyone.

@procload
Copy link
Author

@shvaikalesh Thanks. It'd be great since there's no way I can use Brunch the way it is now without the change... and I really want to!

@hbobenicio
Copy link

Same issue here. I'm behind a proxy and even with
brunch new hello-brunch -s https://github.com/brunch/with-es6
it replaces the protocol to git
log: Cloning git repo "git://github.com/brunch/with-es6.git"

probably some flag like
brunch new hello-brunch -s es6 -https
or simply allowing
-s https://github.com/brunch/with-es6
without replacing the protocol would be great, IMHO.

@Dylanderv
Copy link

Using this can solve the problem
git config --global url.https://github.com/.insteadOf git://github.com/

@paulmillr paulmillr added the bug label Aug 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

5 participants