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

Support configuring the interface (i.e. host) the server will listen to #161

Open
iamFIREcracker opened this issue Mar 29, 2022 · 1 comment · May be fixed by #167
Open

Support configuring the interface (i.e. host) the server will listen to #161

iamFIREcracker opened this issue Mar 29, 2022 · 1 comment · May be fixed by #167

Comments

@iamFIREcracker
Copy link

  • I am trying to integrate livereload with an Express application running on Replit
    • When deployed there, Replit assigns you a hostname
    • It proxies all incoming connections to your service, so long as it listened to 0.0.0.0
  • To make this all work I then need the Express application to listen on 0.0.0.0 (not a big deal, it's the default)
  • I also need to tell livereload to listen on a a different interface, e.g. 127.0.0.1
    • But this, unfortunately is currently not supported

Is there appetite for adding an additional config, host, for livereload to use while creating the listening server? Let me know, I have already pushed some changes into my branch, and it will not take me much to create a PR off of it.

Thanks,
M.

@napcs
Copy link
Owner

napcs commented May 10, 2022

@iamFIREcracker Yea I'm not opposed to this. Let's use -b for the CLI option, and --bind for the long option, and bindHost as the argument?

Do you want to make a PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants