mirror of
https://github.com/Jackett/Jackett
synced 2024-12-23 00:08:23 +00:00
Updated Renaming Indexers (markdown)
parent
36b20c5a80
commit
1679f7132a
1 changed files with 1 additions and 1 deletions
|
@ -10,7 +10,7 @@ Note that changing the id must be justified.
|
||||||
* c#: rename the file and the class name (not need to change `src/Jackett.Updater/Program.cs`)
|
* c#: rename the file and the class name (not need to change `src/Jackett.Updater/Program.cs`)
|
||||||
4. Optional: The tracker name / description is not related to the id and it can be changed anytime
|
4. Optional: The tracker name / description is not related to the id and it can be changed anytime
|
||||||
|
|
||||||
## How does it works for the user
|
## How it works for the user
|
||||||
1. The updater will remove the old .yaml definition (if it's a .yaml indexer) and the new one will be extracted in the folder.
|
1. The updater will remove the old .yaml definition (if it's a .yaml indexer) and the new one will be extracted in the folder.
|
||||||
2. In the first start, Jackett will rename the old configuration file into the new one. The user will see this trace. `Info Configuration renamed: /home/XX/.config/Jackett/Indexers/nostalgic.json => /home/XX/.config/Jackett/Indexers/vhstapes.json `
|
2. In the first start, Jackett will rename the old configuration file into the new one. The user will see this trace. `Info Configuration renamed: /home/XX/.config/Jackett/Indexers/nostalgic.json => /home/XX/.config/Jackett/Indexers/vhstapes.json `
|
||||||
3. The indexer is able to load the previous configuration without problem. From this moment, there are no longer remains of the old id.
|
3. The indexer is able to load the previous configuration without problem. From this moment, there are no longer remains of the old id.
|
||||||
|
|
Loading…
Reference in a new issue