


An advantage of this approach is that Subsonic does not need to be aware of SSL settings, and it can be left with default settings. The following configuration makes lighttpd accept HTTPS connections and proxies them to localhost. var/lib/subsonic/subsonic.sh SUBSONIC_CONTEXT_PATH=/subsonic To run Subsonic under a different path, you have to set the following options: Proxy_set_header X-Forwarded-Proto https Proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for The following nginx configuration runs Subsonic under : If you already have multiple web services running, it might be easier to use a single SSL configuration everywhere. You will still be able to re-navigate to port 8080 after the warning page and have it work on that port. When attempting to change it to port 8080 it will automatically redirect the browser to port 8443 after manually accepting the invalid HTTPS certificate. Note: port 8443 seems hard-coded somewhere. To enable HTTPS browsing and streaming, edit /var/lib/subsonic/subsonic.sh and change this line: # for transcoder in ffmpeg flac lame do ln -s "$(which $transcoder)" done Instead, the user must create symlinks to the transcoders in the /var/lib/subsonic/transcode folder.
#Sublime mp3 index install
You should therefore install the ffmpeg, and you may also want to install flac and lame.įor security reasons, Subsonic will not search the system for any transcoders. After installation, you can change these defaults so that, for example, Subsonic will transcode FLAC files using FLAC and LAME instead of FFmpeg. Hence it is recommended for users to instead install the open-source fork airsonic-advanced-git AUR.Īfter performing any configuration, remember to restart rvice.īy default, Subsonic uses FFmpeg to transcode videos and songs to an appropriate format and bitrate on-the-fly.
#Sublime mp3 index software
In addition, as of version 6, the software was not open source. The old, unmaintained version of subsonic AUR is still available.
