Updated proxy doc

Signed-off-by: Andrew DeMaria <lostonamountain@gmail.com>
master
Andrew DeMaria 8 years ago
parent 438589c3cf
commit 9292c457c9
No known key found for this signature in database
GPG Key ID: 0A3F5E91F8364EDF
  1. 33
      documentation/PROXY.md

@ -20,25 +20,32 @@ free.
## Libresonic configuration ## Libresonic configuration
A few settings can be tweaked in Libresonic's startup script or Tomcat A few settings should be tweaked via Spring Boot or Tomcat
configuration. configuration:
The reverse proxy will handle HTTPS connections, so there is no need for - Set the context path to `/libresonic`
Libresonic to handle them, which is why we set `httpsPort` to 0: - Set the correct address to listen to
- Set the correct port to listen to
libresonic.httpsPort=0 #### Spring Boot
Furthermore, the internal Libresonic server should only be accessible from the Add the following java args:
inside of the reverse proxy : we tell Libresonic to listen on the local IP
only:
libresonic.host=127.0.0.1 ```java -Dserver.port=4040 -Dserver.address=127.0.0.1 -Dserver.contextPath=/libresonic -jar libresonic.war```
libresonic.port=4040
Finally, if Libresonic should be accessible from a subdirectory, the context #### Tomcat
path must be set correctly: Modify your `<Connector>` with the proper address and port:
libresonic.contextPath=/libresonic ```
<Connector
port="4040"
address="127.0.0.1"
...
```
See [HTTP Connector](https://tomcat.apache.org/tomcat-7.0-doc/config/http.html) for further detail.
For the context path, tomcat will automatically deploy to a context path matching your war name. So if you're using
libresonic.war, you do not need to change anything.
## Reverse proxy configuration ## Reverse proxy configuration

Loading…
Cancel
Save