2017-12-23 14:07:45 +01:00
|
|
|
---
|
2019-10-26 12:04:54 +02:00
|
|
|
date: 2019-10-26T11:04:03+01:00
|
2017-12-23 14:07:45 +01:00
|
|
|
title: "rclone config create"
|
|
|
|
slug: rclone_config_create
|
|
|
|
url: /commands/rclone_config_create/
|
|
|
|
---
|
|
|
|
## rclone config create
|
|
|
|
|
|
|
|
Create a new remote with name, type and options.
|
|
|
|
|
|
|
|
### Synopsis
|
|
|
|
|
|
|
|
|
|
|
|
Create a new remote of <name> with <type> and options. The options
|
|
|
|
should be passed in in pairs of <key> <value>.
|
|
|
|
|
|
|
|
For example to make a swift remote of name myremote using auto config
|
|
|
|
you would do:
|
|
|
|
|
|
|
|
rclone config create myremote swift env_auth true
|
|
|
|
|
2019-02-09 11:42:57 +01:00
|
|
|
Note that if the config process would normally ask a question the
|
|
|
|
default is taken. Each time that happens rclone will print a message
|
|
|
|
saying how to affect the value taken.
|
|
|
|
|
2019-06-15 13:01:29 +02:00
|
|
|
If any of the parameters passed is a password field, then rclone will
|
|
|
|
automatically obscure them before putting them in the config file.
|
|
|
|
|
2019-02-09 11:42:57 +01:00
|
|
|
So for example if you wanted to configure a Google Drive remote but
|
|
|
|
using remote authorization you would do this:
|
|
|
|
|
|
|
|
rclone config create mydrive drive config_is_local false
|
|
|
|
|
2017-12-23 14:07:45 +01:00
|
|
|
|
|
|
|
```
|
|
|
|
rclone config create <name> <type> [<key> <value>]* [flags]
|
|
|
|
```
|
|
|
|
|
|
|
|
### Options
|
|
|
|
|
|
|
|
```
|
|
|
|
-h, --help help for create
|
|
|
|
```
|
|
|
|
|
2019-06-20 17:18:02 +02:00
|
|
|
See the [global flags page](/flags/) for global options not listed here.
|
|
|
|
|
2017-12-23 14:07:45 +01:00
|
|
|
### SEE ALSO
|
2018-03-19 11:06:13 +01:00
|
|
|
|
2017-12-23 14:07:45 +01:00
|
|
|
* [rclone config](/commands/rclone_config/) - Enter an interactive configuration session.
|
|
|
|
|