Skip to content
This repository has been archived by the owner on Feb 25, 2019. It is now read-only.

Does not readily work with boot2docker on OS X #2

Open
henrjk opened this issue Jul 10, 2015 · 0 comments
Open

Does not readily work with boot2docker on OS X #2

henrjk opened this issue Jul 10, 2015 · 0 comments

Comments

@henrjk
Copy link
Contributor

henrjk commented Jul 10, 2015

I started trying this out on OS X with docker and boot2docker

mac:connect-example-angularjs dev$ docker -v
Docker version 1.6.0, build 4749651
mac:connect-example-angularjs dev$ boot2docker -v
Boot2Docker-cli version: v1.6.0
Git commit: 9894ae9

In my scenario I first setup [Anvil Connect authorization server (https://github.com/anvilresearch/connect/blob/master/README.md). As a result the Anvil Authorization server runs on localhost:3000.

The first stumbling block was that inplace sed editing is not easily portable between linux and OSX versions of sed. After a workaround this worked for me. One thing that was not so good was that the in place changes made it harder to see what other changes were made in the same file.

Then I followed the setup in this readme, but things would not work. After @oren and @christiansmith helped me out on gitter, I was able to get this going remembering that with boot2docker one had to connect to boot2docker ip. So instead of connecting to localhost:9000 one had to connect to 192.168.59.103:9000.

However the browser showed an html file which looked bare of style. The problem was that the bower_components were not served, so all scripts were missing.

After correcting this things seemed to work better and if I recollect correctly I fixed a few things regarding mismatches of the anvil connect server client registration with the requests that were made by the app.

It took me a while to notice that how the authentication redirect worked. The key was that the callback redirect actually served angular index.html under the name callback as this was not defined. I am not sure whether I had introduced this with my tweaks or whether this was intentional. As a result angular would reload completely.

This is different when using a display popup request with the proper callback.
I have documented with some screenshot the interaction I am now seeing with the popup callback in my fork (intended to become a PR).

For better debugging I disabled the session stuff in my fork also.

Should the changes I made be incorporated into this repository?

PS I am planning to add a short section in the README.md to clarify usage without docker and grunt serve.

@henrjk henrjk mentioned this issue Jul 14, 2015
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant