qsctl
qsctl is intended to be an advanced command line tool for QingStor, it provides powerful unix-like commands to let you manage QingStor resources just like files on local machine. Unix-like commands contains: cp, ls, mb, mv, rm, rb, and sync. All of them support batch processing.
Installation
virtualenv:
$ pip install qsctl
System-Wide:
$ sudo pip install qsctl
On Windows systems, run it in a command-prompt window with administrator privileges, and leave out sudo.
Getting Started
To use qsctl, there must be a configuration file , for example:
access_key_id: 'ACCESS_KEY_ID_EXAMPLE' secret_access_key: 'SECRET_ACCESS_KEY_EXAMPLE'
The configuration file is ~/.qingstor/config.yaml by default, it also can be specified by the option -c /path/to/config.
You can also config other option like host , port and so on, just add lines below into configuration file, for example:
host: 'qingstor.com' port: 443 protocol: 'https' connection_retries: 3 # Valid levels are 'debug', 'info', 'warn', 'error', and 'fatal'. log_level: 'debug'
Available Commands
Commands supported by qsctl are listed below:
ls |
List QingStor keys under a prefix or all QingStor buckets. |
cp |
Copy local file(s) to QingStor or QingStor key(s) to local. |
mb |
Create a QingStor bucket. |
rb |
Delete an empty QingStor bucket or forcibly delete nonempty QingStor bucket. |
mv |
Move local file(s) to QingStor or QingStor key(s) to local. |
rm |
Delete a QingStor key or keys under a prefix. |
sync |
Sync between local directory and QingStor prefix. |
presign |
Generate a pre-signed URL for an object. |
Examples
List keys in bucket <mybucket> by running:
$ qsctl ls qs://mybucket Directory test/ 2016-04-03 11:16:04 4 Bytes test1.txt 2016-04-03 11:16:04 4 Bytes test2.txt
Sync from QingStor prefix to local directory:
$ qsctl sync qs://mybucket3/test/ test/ File 'test/README.md' written File 'test/commands.py' written
See the detailed usage and more examples with ‘qsctl help’ or ‘qsctl <command> help’.
Release files for qsctl 1.7.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qsctl-1.7.7.tar.gz | 30.3 kB | Without provenance | Details for qsctl-1.7.7.tar.gz |
Release files / qsctl-1.7.7.tar.gz
| Download URL | qsctl-1.7.7.tar.gz |
|---|---|
| Size | 30.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c0ea8ec9f5d5c69256a6b0830a9bfd253d9f14ba7c9475bb3600f780cfc40ab
|
|
BLAKE2b-256 checksum How to use checksums |
f2f8de503b3bbcb0b7739344fd5a82b12e62f0e5876bc42e3d557d926d5c2f54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.6
|
Security for qsctl 1.7.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
