Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Params -dry-run | -v | \ in path doesn't work on Windows #16

Open
sunnyd24 opened this issue Jan 10, 2024 · 2 comments
Open

Params -dry-run | -v | \ in path doesn't work on Windows #16

sunnyd24 opened this issue Jan 10, 2024 · 2 comments

Comments

@sunnyd24
Copy link

It seems the windows binary v1.5 doesn't accept -dry-run or -v as params, as per readme file excerpt below:

There are also some optional params:
-v Enables verbose logging
-dry-run will scan the folder for video files, but not call the Sonarr API

The command I am using is below with the error output:

SonarrAutoImport -dry-run
[11:21:52.373--INF] === Sonarr Auto Import Log Started ===
[11:21:52.430--INF] LogLevel: Information
[11:21:52.517--ERR] Settings not found: ry-run

I have found that the readme needs updating to reflect 3 things if using windows:

  1. use --dry-run instead of -dry-run
  2. use --v instead of -v
  3. use double backslashes in paths

Also, the readme could do with a good description as to the difference between "mappingPath" and "downloadsFolder". This has been provided in a separate issue by @ jortan with thanks.

Originally posted by @jortan in #10 (comment)

downloadsFolder is the path to media files to be processed from the perspective of SonarrAutoImport script
mappingPath is the path to media files to be processed from the perspective of Sonarr

These should point to the same destination. In some scenarios (docker) the same destination might require a different path.
@Webreaper
Copy link
Owner

Sounds good - want to submit a PR with the appropriate readme changes?

@sunnyd24
Copy link
Author

Sounds good - want to submit a PR with the appropriate readme changes?

Happy to but I haven't done this before. I think this is the process looking at GitHub help, could you confirm?

  1. You need to assign me to this issue
  2. I create a pull request
  3. I make changes to readme.md
  4. I send to you for review/approval
  5. You merge changes and up-issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants