couchbaselabs/WebSockets-Cocoa

[Todd Orler]

I'm trying to get set up with the "stable" branch, and noticed that there's a new submodule since the last time we integrated CBL iOS:  WebSockets-Cocoa.  However, when I try to clone this, as described in the .gitmodules file, it fails.  Searching for this couchbaselabs repo also fails to find anything.

Thoughts?

Thanks,
-Todd

[Jens Alfke]

On Apr 16, 2014, at 1:05 PM, Todd Orler <tod...@hammersmith.mygbiz.com> wrote:

I'm trying to get set up with the "stable" branch, and noticed that there's a new submodule since the last time we integrated CBL iOS:  WebSockets-Cocoa.  However, when I try to clone this, as described in the .gitmodules file, it fails. 

All you should need to do is run

git pull

git submodule sync

git submodule update --recursive

I’ve seen problems with registering a new submodule that has its own submodules … so you may also need to do

cd vendor/WebSockets-Cocoa

git submodule init --recursive

git submodule update

 Searching for this couchbaselabs repo also fails to find anything.

It’s https://github.com/couchbaselabs/WebSockets-Cocoa

—Jens

[Todd Orler]

Thanks, Jens!  I'm up and running now.

All you should need to do is run

git pull

git submodule sync

git submodule update --recursive

This was failing for me, because we require the HTTPS cloning protocol, due to some firewall issue (which I don't fully understand).  Your .gitmodules file (at the root of the couchbase-lite-ios repo) uses the "git://github.com..." protocol.  We've gotten around this in the past by putting a copy of those submodule definitions into our own .gitmodules file at our own repo root, and using HTTPS instead of GIT.  But for some reason, even this didn't work - probably because WebSockets-Cocoa contains its own submodules.  I don't really understand the whole submodule thing, but switching your .gitmodules file to use HTTPS protocol worked.  Any reason why your .gitmodules file uses GIT protocol, while the WebSockets-Cocoa folder's .gitmodules file uses HTTPS protocol?  It sure would make our lives easier if you used HTTPS protocol everywhere.
 

I’ve seen problems with registering a new submodule that has its own submodules … so you may also need to do

cd vendor/WebSockets-Cocoa

git submodule init --recursive

git submodule update

I definitely needed to cd to the WebSockets-Cocoa folder, and init from there (although --recursive isn't a valid argument for "init"). 

 

 Searching for this couchbaselabs repo also fails to find anything.

It’s https://github.com/couchbaselabs/WebSockets-Cocoa

Yep, my mistake there.

Thanks,
-Todd

[Jens Alfke]

On Apr 16, 2014, at 3:51 PM, Todd Orler <tod...@hammersmith.mygbiz.com> wrote:

we require the HTTPS cloning protocol, due to some firewall issue (which I don't fully understand).

Probably because HTTPS is so incredibly secure (cough, cough.) But seriously, I think the git: scheme uses SSH, and maybe your firewall doesn’t allow SSH for some reason?

Any reason why your .gitmodules file uses GIT protocol, while the WebSockets-Cocoa folder's .gitmodules file uses HTTPS protocol?  It sure would make our lives easier if you used HTTPS protocol everywhere.

Not really; I usually just copy and paste the clone URLs from the Github repo web page, so that’s probably what it decided to give me at the time. I’m honestly not too clear on the functional differences between git: and https: repo URLs.

I believe you can just edit the .gitmodules file and change the URLs in there, then do “git submodule sync”.

—Jens