The way OpenRepeater works is the settings in the web UI are saved into a database, then those settings are used to construct the proper config files when changes are made. Generally speaking I would say it is not typically possible to upgrade the software as historically speaking with each progressive version there have been gradual changes to the database structure that could cause issues migrating the data.
It would likely be best to take screen shots of your setting and apply the same settings in the new version. If you have any custom sound files, be sure to make backups of those and upload those into the new version.
In the upcoming version 2.1.0 we have added a backup and restore feature. This will backup the database, modules, customs sound files, and ALSA settings. Going forward from here, you will be able to attempt to restore a backup to a newer version, but ORP will warn you if there is a version mismatch between the backup file and the current version. This will be a great feature for migrating installations to a different controller, recovering from a failure, or making restore points if you want to experiment.
The backup is a single file with ‘.orp’ extension. This is just an archive file and you can unzip it by changing the extension to ‘.tar.gz’.
73,
Aaron – N3MBH / WRFV871
OpenRepeater is offered free of charge. Find out how you can support us.
.
.