add explicit migration info

Jakob Ketterl 2021-04-26 19:41:48 +02:00
parent 26d30ce466
commit 7c2a543877
1 changed files with 9 additions and 3 deletions

@ -12,7 +12,8 @@ system taking precedence.
It will not update the old configuration files, but instead write all changes to the new storage system. In
combination, that means that as soon as you start editing the configuration using the new web configuration, your
existing settings, along with the modifications, will be written to the new storage system, and your previous
configuration files will become obsolete. This should ensure a seamless, transparent migration of existing configurations.
configuration files will become obsolete. This should ensure an implicit, seamless and transparent migration of existing
configurations.
Future versions of OpenWebRX will eventually drop the support for the old config files. At this point, the transition
to the new config system will be complete.
@ -52,10 +53,15 @@ the changes you make in the web configuration, you will need to mount an additio
Once the migration is complete, the existing volume for `/etc/openwebrx` is only used for the remaining `bands.json`
and `openwebrx.conf`. If you don't have any modifications to these files, you should be able to run without this volume.
## Explicit migration
If you want to migrate your configuration right away, or want to make sure that all settings have been transferred to
the new configuration system, you can run an explicit migration using the command `openwebrx config migrate`.
# Red Pitaya support
The existing "red_pitaya" device type has been dropped in favor of the new HPSDR support, which also covers the Red
Pitaya devices.
The existing "red_pitaya" device type has been dropped in favor of the new HPSDR support, which also covers Red Pitaya
devices.
# `rtltcp_compat` changes