We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am trying to use this tool for the first time and wish to do a dry run to test it out.
I installed nodejs 6.x and it included adding npm to the my path envronment.
I then installed plex-sync using npm in the way described in your readme but had to remove the '$' at the beginning as it was not recognised.
Now i am tying to do my first dry run using: DRY_RUN=1 plex-sync http://1234567890.ams.plex.services:80/2 192.168.1.8/2
but i get the error:
'DRY_RUN' is not recognized as an internal or external command, operable program or batch file.
Sorry i know its going to be a simple solve but I have not used programs like this before
The text was updated successfully, but these errors were encountered:
You can set environment variable first and then execute rest of the command. This should do it for you.
set DRY_RUN=1 plex-sync http://1234567890.ams.plex.services:80/2 192.168.1.8/2
Sorry, something went wrong.
No branches or pull requests
I am trying to use this tool for the first time and wish to do a dry run to test it out.
I installed nodejs 6.x and it included adding npm to the my path envronment.
I then installed plex-sync using npm in the way described in your readme but had to remove the '$' at the beginning as it was not recognised.
Now i am tying to do my first dry run using:
DRY_RUN=1 plex-sync http://1234567890.ams.plex.services:80/2 192.168.1.8/2
but i get the error:
'DRY_RUN' is not recognized as an internal or external command,
operable program or batch file.
Sorry i know its going to be a simple solve but I have not used programs like this before
The text was updated successfully, but these errors were encountered: