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.

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

Starting signalhub-server internal #135

Open
stritti opened this issue Nov 17, 2017 · 2 comments
Open

Starting signalhub-server internal #135

stritti opened this issue Nov 17, 2017 · 2 comments

Comments

@stritti
Copy link
Contributor

stritti commented Nov 17, 2017

For local installation it would be cool to add possibility to start the hub internal. something like:

var hub = signalhub('robotopia', [
  P2P_CONFIG.habUrl
])
@timgrossmann
Copy link
Member

@stritti Just to make sure I understand this right.

Instead of the provided SignalHub server you want to run Robotopia locally and use your own SignalHub server instead of the provided on.

If it's the case that you want to run it locally anyway you can simply edit this:

robotopia/index.js

Lines 1 to 4 in 38e43f1

const P2P_CONFIG = {
hubUrl: 'https://signalhub.perguth.de:65300/'
// hubUrl: 'localhost:8080'
}

And build and start it on your own system.

If this is not what you meant, feel free to open this issue again.
Thank you

@stritti
Copy link
Contributor Author

stritti commented Nov 21, 2017

Hi @timgrossmann thanks for the pointer. I found this,

The base issue was, that you will receive a CORS-Exception if you run the project locally (also on robotopia.co) using existing hub. See console of browser if you run presenter mode: http://robotopia.co/#presenter ->

No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://robotopia.co' is therefore not allowed access. The response had HTTP status code 403.

To get a easy setup to run, I thought it could be a good idea to add the hub internally.

BTW, I switched for now to https://signalhub-jccqtwhdwc.now.sh/, which works for me for the moment.

@timgrossmann timgrossmann reopened this Nov 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants