Not sure if I'm doing it wrong.

[darron]

Can't get it to work with my own Docker server:

https://gist.github.com/darron/7906034

Also can't get it to build on OS X for some reason.

Everything's in the gist.

Any tips?

[progrium]

You might need to delete some of the packages in pkg as it seems some where built with different versions of Go. Deleting and running go get to rebuild them should use latest Go.

Not sure why it's not able to connect. I just pushed a newer version you could try. It had some buggy copilot connect code before.

[darron]

Very cool - that worked on OS X.

Still no dice with the Dockerfile - it builds and connects but doesn't ever
actually come back - still does this:

https://gist.github.com/darron/7906402

On Wed, Dec 11, 2013 at 12:06 AM, Jeff Lindsay notifications@github.comwrote:

You might need to delete some of the packages in pkg as it seems some
where built with different versions of Go. Deleting and running go get to
rebuild them should use latest Go.

Not sure why it's not able to connect. I just pushed a newer version you
could try. It had some buggy copilot connect code before.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-30299081
.

[progrium]

Well the URL will definitely be wrong, it's hardcoded for that domain.
Still not sure what could be the problem. Let me know what you find.

On Tue, Dec 10, 2013 at 11:38 PM, darron froese notifications@github.comwrote:

Very cool - that worked on OS X.

Still no dice with the Dockerfile - it builds and connects but doesn't
ever
actually come back - still does this:

https://gist.github.com/darron/7906402

On Wed, Dec 11, 2013 at 12:06 AM, Jeff Lindsay notifications@github.comwrote:

You might need to delete some of the packages in pkg as it seems some
where built with different versions of Go. Deleting and running go get
to
rebuild them should use latest Go.

Not sure why it's not able to connect. I just pushed a newer version you
could try. It had some buggy copilot connect code before.

—
Reply to this email directly or view it on GitHub<
https://github.com/progrium/termshare/issues/1#issuecomment-30299081>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-30300226
.

Jeff Lindsay
http://progrium.com

[darron]

Ahh - ok - will keep trying.

Thought maybe passing -s="termshare.octohost.io:80" would output a
different URL - no worries.

On Wed, Dec 11, 2013 at 12:42 AM, Jeff Lindsay notifications@github.comwrote:

Well the URL will definitely be wrong, it's hardcoded for that domain.
Still not sure what could be the problem. Let me know what you find.

On Tue, Dec 10, 2013 at 11:38 PM, darron froese notifications@github.comwrote:

Very cool - that worked on OS X.

Still no dice with the Dockerfile - it builds and connects but doesn't
ever
actually come back - still does this:

https://gist.github.com/darron/7906402

On Wed, Dec 11, 2013 at 12:06 AM, Jeff Lindsay notifications@github.comwrote:

You might need to delete some of the packages in pkg as it seems some
where built with different versions of Go. Deleting and running go get
to
rebuild them should use latest Go.

Not sure why it's not able to connect. I just pushed a newer version
you
could try. It had some buggy copilot connect code before.

—
Reply to this email directly or view it on GitHub<
https://github.com/progrium/termshare/issues/1#issuecomment-30299081>
.

—
Reply to this email directly or view it on GitHub<
https://github.com/progrium/termshare/issues/1#issuecomment-30300226>
.

Jeff Lindsay
http://progrium.com

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-30300338
.