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.

Sign up for GitHub

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

Jump to bottom

in docker environment livereload on the browser tries to connect to the internal docker ip address of the frontend container #278

Open
chesty opened this issue Jun 22, 2018 · 1 comment · May be fixed by #324
Open

in docker environment livereload on the browser tries to connect to the internal docker ip address of the frontend container #278

chesty opened this issue Jun 22, 2018 · 1 comment · May be fixed by #324

Comments

@chesty
Copy link

chesty commented Jun 22, 2018

I'm using both of the official osrm-frontend and osrm-backend docker containers, after loading the frontend in a browser everything works well except the browser tries to connects to the internal ip address of the frontend server.

I guess we need a way to configure livereload to supply the external ip address?

Project-OSRM/osrm-backend#5119
@EricsonK
Copy link

To prevent the loading of livereload.js on production server...

Open the package.json file,
Edit the line,
"start-index": "budo src/index.js --serve=bundle.js --live -d | bistre",
To,
"start-index": "budo src/index.js --serve=bundle.js -d | bistre",

Removing the --live flag prevent loading of livereload.js

For reference, Budo Github

madmath03 added a commit to Monogramm/osrm-frontend that referenced this issue Jun 18, 2020
@madmath03
✨ Start-prod without livereload fix Project-OSRM#278
ed39fcf
This was referenced Jun 18, 2020
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@chesty @EricsonK