-
Notifications
You must be signed in to change notification settings - Fork 71
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
Chrome: Use current domain as host #15
Comments
I had the same issue myself. It would definitely be a useful feature. |
+1. This would be a welcome addition to the feature set. |
+1, would help a lot with Docker development. |
+1 |
Please, anyone found a workaround? |
If you include the script manually will work:
But this should be fixed ASAP. |
Guys, a change to try to connect to both 127.0.0.1 and the tab's host is planned. I cannot make it connect to only the tab's host because that will break valid remote use cases of my app. (The app can override remote CSS files with local ones, so users can be editing styles for a site running remotely.) |
@andreyvit how about merging #35 ? |
@camilonova But I've just explained why #35 cannot be merged. :-) The only way to solve this is to try to connect to both hosts. I'll get to that soon. If someone wants to do a pull request sooner, I'll be happy to merge it. |
@andreyvit Thank you, do you have any updates about this? |
@camilonova Nope, I didn't mean that soon. Contributions are still welcome. :-) |
@andreyvit If you give me some directions I can try to do it on my own |
+1 |
@andreyvit any updates? |
+10000 |
Do we have any updates, or there is way I can help? |
I have just upload a custom version that allow set your custom host and port: |
+1 for having ability to configure host/port (or least host, or at least use current website domain). Required to be able to use extension while developing in Docker. |
I'm developing on a dev server so the host is not http://localhost. It would be nice to have the chrome extension use the current host instead of defaulting to 127.0.0.1.
The text was updated successfully, but these errors were encountered: