-
Notifications
You must be signed in to change notification settings - Fork 17
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
Publicly exposed baseURL #150
Comments
If you are running MS with the docker image then preventing access is as easy as not publishing the port when running the container (don't use If you are running locally (with npm/node from the command line) I've added the ability to disable the web server in the
If you do this correctly you'll see this in the log on startup
|
Yeah, just as I thought it would break the webhooks/Tautulli as a source if the webserver was offline heh |
This feature is now available in v0.7.1. |
Additional context
Hello, thanks for this project it's working great as expected, however I was a tad concerned about the security of the web server being exposed (not on the default port of 9078)
I don't have the ability to configure a reverse proxy or http auth due to shared host restrictions on the vps (though I assume that would break webhooks altogether and the purpose of the whole thing), is it possible to have it not launch the web server and log only? i'm not too concerned atm, the only thing a person could do is restart the brainz client I have configured. Any suggestions?
The text was updated successfully, but these errors were encountered: