Backup and Restore function about radio-api HOT 6 CLOSED

I added the feature in Version 2.7.2.

After the Update a token CONF_IM_EXPORT_TOKEN needs to be set in config. Using this token the Im- & Export interface can be used at ./gui/im-export.php.

Relying on a token shown in a radio did not convince me, as there might be multiple radios and one user could overwrite the settings of another user. Thus, I added the token via the config, which can be interpreted as an admin password.

from radio-api.

Hi,

currently a backup would require to run the /cron.php once and then save the entire ./data folder (of json files). So, from a terminal on the server a backup could be created with something like
docker exec --user www-data radio_api sh -c "php /cron.php; tar -czvf /php-code/data/backup.tar.gz /php-code/data/*.json",
which creates a backup.tar.gz in the ./data folder containing all radio configuration and data.

The backup can be restored or imported to a new radio by extracting backup.tar.gz to the ./data folder and (re-)starting the Docker container.

(This assumes the use of the Docker mode, without Docker check the update instructions here.)

Regarding a backup & restore or ex- & import feature I see the following problem:
Currently there is no user management besides the GUI Code for each radio.
Especially there are no admin accounts or user levels, which could be used to authenticate a user which is allowed to download an export or upload an import.

So one possibility would be to provide a command line script on the server for creating backups, but this mostly already exists as described above.

Another possibility would be to introduce real user accounts with different levels like „admin“, but this would be a huge change of Radio-API and its overall structure. And of course also much work, too.

The last possibility would be to create some small im- & export web interface which uses a token defined in the configuration for authentication. This interface would only provide two features „export“ a file and „import“ a file.

It guess only the last possibility would be realistic to implement, but I am a bit unsure if this would really be sensible: The command line based backup and restore should work well and when setting up a new instance or importing a backup still manual steps using the command line are necessary. Thus, a web interface would not be a huge benefit?
And for regular backups a automatic cron job may be created.

from radio-api.

One More issue : On Solr Collection Data Backup Based on Condition/Data Filter.(There is no provision for that . )

Because SOLR BACKUP API with Query is not working
//http://localhost:8983/solr/admin/collections?action=RESTORE&name=myBackupName&location=C:\Users\DELL\Downloads\SOLR_BACKUP&collection=myCondCollection&query=text:cellphone

I am trying out to perform backups of our Solr data with a particular condition in mind.

To provide some context, let's say Solr collection consists of 100 records, among which 70 records contain the text "mobile," and the remaining 30 records contain the text "cellphone." my objective is to take a Solr collection/data backup that contains only the records the text "cellphone" – essentially, we want to create a backup file that reflects these 30 specific records only.

I would greatly appreciate it if you could share insights on the best practices or methods to achieve this selective backup based on a condition. If there are specific parameters or commands we should be utilizing, kindly provide the necessary guidance. Additionally, any documentation or references you could point us to would be immensely helpful.

Thank you in advance for your time and assistance. We value your expertise and look forward to implementing an efficient solution based on your recommendations.

from radio-api.

Radio-API does not use Solr and thus does not provide any Solr API access. The comment seems to be out of context here, thus I will hide it.

from radio-api.

Creating a whole user account management just for this would be a show stopper.

Being able to import and export the settings view the gui would be a helpful feature in my opinion.

Maybe it would help to implement something else to avoid a misuse of this feature. Imaging I would press the import button and I have to enter a code, which is only shown on the radio. So I have to be in front of the radio / I have to have access to the radio to be able to import the settings. This would make sure that only people how know what the do will overwrite the settings. Would this be a simple method?

Thank you
Stoneubi

from radio-api.

Wow perfect. Thank you very much.

from radio-api.