Can't set where Exportarr saves to #5
Comments
santiagosayshey
added a commit
that referenced
this issue
Jan 27, 2024
- changed from json to yaml for config - added export_path setting to set where exported files go : fixes #5 - exports now save to {export_path}/{app_type}/{app_name} - can choose which instance to manually import to - sync automatically chooses correct custom formats / quality profiles for the app type - updated readme with usage examples - added install requirements
Merged
santiagosayshey
added a commit
that referenced
this issue
Jan 27, 2024
- changed from json to yaml for config - added export_path setting to set where exported files go : fixes #5 - exports now save to {export_path}/{app_type}/{app_name} - can choose which instance to manually import to - sync automatically chooses correct custom formats / quality profiles for the app type - updated readme with usage examples - added install requirements Closes #4, #5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
The current behavior in the Radarr import/export process, as discussed in issue #4, leads to an unintentional overwriting of the existing Custom Formats file. This results in users having to redownload the file to import their desired quality profiles correctly.
The problem arises when exportarr is executed before importarr, leading to the overwriting of the original custom_format (Radarr).json file. This scenario was not initially considered during the development of the import/export functionality.
Proposed Fix:
Set a path in the config file to choose where files are exported to. This keeps dev functionality, while also being user friendly, Path can be set to the 'master' instance (The folder in which people import from), or anywhere else.
Fixes #4
The text was updated successfully, but these errors were encountered: