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
Scripts on the README.md page are mostly all on one line, e.g.
#!/bin/bash cd /usr/lib/archivematica/automation-tools/ /usr/share/python/automation-tools/bin/python -m transfers.transfer --user <user> --api-key <apikey> --ss-user <user> --ss-api-key <apikey> --transfer-source <transfer_source_uuid> --config-file <config_file>
This becomes easier to scroll if we do something along these lines:
#!/bin/bash cd /usr/lib/archivematica/automation-tools/ /usr/share/python/automation-tools/bin/python -m transfers.transfer --user <user> \ --api-key <apikey> \ --ss-user <user> \ --ss-api-key <apikey> \ --transfer-source <transfer_source_uuid> --config-file <config_file>
The text was updated successfully, but these errors were encountered:
I find the following more readable:
#!/usr/bin/env bash cd /usr/lib/archivematica/automation-tools/ /usr/share/python/automation-tools/bin/python \ -m transfers.transfer \ --user <user> \ --api-key <apikey> \ --ss-user <user> \ --ss-api-key <apikey> \ --transfer-source <transfer_source_uuid> \ --config-file <config_file>
Sorry, something went wrong.
ross-spencer
No branches or pull requests
Scripts on the README.md page are mostly all on one line, e.g.
This becomes easier to scroll if we do something along these lines:
The text was updated successfully, but these errors were encountered: