Don't Overwrite - /usr/share/subsonic/subsonic.sh on Upgrade

[jchawk3]

When installing the debian package of subsonic the package fails to check if /usr/share/subsonic/subsonic.sh start up script has been modified and instead overwrites it.

This is an inconvenience because each time I upgrade I have to remember to go in and edit this script to update it with my personal preferences such as port number, host ip to run on, etc... An alternative approach would be to allow for localized configuration via files in /etc/subsonic/ then have the start up read this configuration file for changes.

Debian's dpkg utility provides the means to validate each configuration file to ensure it will not be over written if it is changed.

Here is a link -- http://www.debian.org/doc/debian-policy ... files.html

Otherwise I have been a happily registered (paid) user for quite sometime! Please keep up the excellent work, I have referred your software to many of my friends! You rock!

[ZonOfthor]

Hi,
also using Subsonic on Linux (Arch).

I would really like to know what files Subsonic uses of settings, eg media folders and user accounts are not saved in subsonic.sh ... What's the easiest way to upgrade Subsonic?

[jonnymnemo]

Hi !

Normally, you don't have to modify subsonic.sh.
To add startup preferences (port, non root user, https...), you have to edit /etc/default/subsonic.

I would really like to know what files Subsonic uses of settings, eg media folders and user accounts are not saved in subsonic.sh ... What's the easiest way to upgrade Subsonic?

Media folders and user accounts are stored in the subsonic.script file, located in /var/subsonic/db.

You can grab some info on how to use this file in this thread :
http://forum.subsonic.org/forum/viewtopic.php?f=2&t=10326

[jchawk3]

Well I noticed this about 6 months late but thanks! I totally spaced on the /etc/default/subsonic config file.

That would indeed be the right place to make the startup configuration adjustments. Thanks!!!