mirror of
https://github.com/dutchcoders/transfer.sh.git
synced 2024-11-23 12:40:19 +01:00
Update README.md (#415)
* Update README.md Add minor grammar improvements. * Update README.md Fix grammar.
This commit is contained in:
parent
2da62eb235
commit
6b8eff8322
1 changed files with 9 additions and 10 deletions
19
README.md
19
README.md
|
@ -51,7 +51,7 @@ $ curl --upload-file ./hello.txt https://transfer.sh/hello.txt -H "Max-Days: 1"
|
||||||
|
|
||||||
### X-Url-Delete
|
### X-Url-Delete
|
||||||
|
|
||||||
The URL used to request the deletion of a file. Returned as a response header.
|
The URL used to request the deletion of a file and returned as a response header.
|
||||||
```bash
|
```bash
|
||||||
curl -sD - --upload-file ./hello https://transfer.sh/hello.txt | grep 'X-Url-Delete'
|
curl -sD - --upload-file ./hello https://transfer.sh/hello.txt | grep 'X-Url-Delete'
|
||||||
X-Url-Delete: https://transfer.sh/hello.txt/BAYh0/hello.txt/PDw0NHPcqU
|
X-Url-Delete: https://transfer.sh/hello.txt/BAYh0/hello.txt/PDw0NHPcqU
|
||||||
|
@ -161,23 +161,23 @@ To use a custom non-AWS S3 provider, you need to specify the endpoint as defined
|
||||||
|
|
||||||
## Storj Network Provider
|
## Storj Network Provider
|
||||||
|
|
||||||
To use the Storj Network as storage provider you need to specify the following flags:
|
To use the Storj Network as a storage provider you need to specify the following flags:
|
||||||
- provider `--provider storj`
|
- provider `--provider storj`
|
||||||
- storj-access _(either via flag or environment variable STORJ_ACCESS)_
|
- storj-access _(either via flag or environment variable STORJ_ACCESS)_
|
||||||
- storj-bucket _(either via flag or environment variable STORJ_BUCKET)_
|
- storj-bucket _(either via flag or environment variable STORJ_BUCKET)_
|
||||||
|
|
||||||
### Creating Bucket and Scope
|
### Creating Bucket and Scope
|
||||||
|
|
||||||
In preparation you need to create an access grant (or copy it from the uplink configuration) and a bucket.
|
You need to create an access grant (or copy it from the uplink configuration) and a bucket in preparation.
|
||||||
|
|
||||||
To get started, login to your account and go to the Access Grant Menu and start the Wizard on the upper right.
|
To get started, log in to your account and go to the Access Grant Menu and start the Wizard on the upper right.
|
||||||
|
|
||||||
Enter your access grant name of choice, hit *Next* and restrict it as necessary/preferred.
|
Enter your access grant name of choice, hit *Next* and restrict it as necessary/preferred.
|
||||||
Aftwards continue either in CLI or within the Browser. You'll be asked for a Passphrase used as Encryption Key.
|
Afterwards continue either in CLI or within the Browser. Next, you'll be asked for a Passphrase used as Encryption Key.
|
||||||
**Make sure to save it in a safe place, without it you will lose the ability to decrypt your files!**
|
**Make sure to save it in a safe place. Without it, you will lose the ability to decrypt your files!**
|
||||||
|
|
||||||
Afterwards you can copy the access grant and then start the startup of the transfer.sh endpoint.
|
Afterwards, you can copy the access grant and then start the startup of the transfer.sh endpoint.
|
||||||
For enhanced security its recommended to provide both the access grant and the bucket name as ENV Variables.
|
It is recommended to provide both the access grant and the bucket name as ENV Variables for enhanced security.
|
||||||
|
|
||||||
Example:
|
Example:
|
||||||
```
|
```
|
||||||
|
@ -196,8 +196,7 @@ For the usage with Google drive, you need to specify the following options:
|
||||||
|
|
||||||
### Creating Gdrive Client Json
|
### Creating Gdrive Client Json
|
||||||
|
|
||||||
You need to create a Oauth Client id from console.cloud.google.com
|
You need to create an OAuth Client id from console.cloud.google.com, download the file, and place it into a safe directory.
|
||||||
download the file and place into a safe directory
|
|
||||||
|
|
||||||
### Usage example
|
### Usage example
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue