2017-12-23 14:07:45 +01:00
|
|
|
---
|
2020-05-27 17:11:47 +02:00
|
|
|
date: 2020-05-27T16:09:49+01:00
|
2017-12-23 14:07:45 +01:00
|
|
|
title: "rclone config create"
|
2020-05-16 16:11:55 +02:00
|
|
|
description: "Create a new remote with name, type and options."
|
2017-12-23 14:07:45 +01:00
|
|
|
slug: rclone_config_create
|
|
|
|
url: /commands/rclone_config_create/
|
2020-02-10 13:31:45 +01:00
|
|
|
# autogenerated - DO NOT EDIT, instead edit the source code in cmd/config/create/ and as part of making a release run "make commanddocs"
|
2017-12-23 14:07:45 +01:00
|
|
|
---
|
2020-05-22 12:17:37 +02:00
|
|
|
# rclone config create
|
2017-12-23 14:07:45 +01:00
|
|
|
|
|
|
|
Create a new remote with name, type and options.
|
|
|
|
|
2020-05-22 12:17:37 +02:00
|
|
|
## Synopsis
|
2017-12-23 14:07:45 +01:00
|
|
|
|
|
|
|
|
2020-05-22 13:22:52 +02:00
|
|
|
Create a new remote of `name` with `type` and options. The options
|
2020-05-25 12:59:33 +02:00
|
|
|
should be passed in pairs of `key` `value`.
|
2017-12-23 14:07:45 +01:00
|
|
|
|
|
|
|
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
|
2020-05-16 16:11:55 +02:00
|
|
|
automatically obscure them if they aren't already obscured before
|
|
|
|
putting them in the config file.
|
|
|
|
|
|
|
|
**NB** If the password parameter is 22 characters or longer and
|
|
|
|
consists only of base64 characters then rclone can get confused about
|
|
|
|
whether the password is already obscured or not and put unobscured
|
|
|
|
passwords into the config file. If you want to be 100% certain that
|
|
|
|
the passwords get obscured then use the "--obscure" flag, or if you
|
|
|
|
are 100% certain you are already passing obscured passwords then use
|
|
|
|
"--no-obscure". You can also set osbscured passwords using the
|
|
|
|
"rclone config password" command.
|
2019-06-15 13:01:29 +02:00
|
|
|
|
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
|
|
|
|
|
|
|
```
|
2020-05-22 13:22:52 +02:00
|
|
|
rclone config create `name` `type` [`key` `value`]* [flags]
|
2017-12-23 14:07:45 +01:00
|
|
|
```
|
|
|
|
|
2020-05-22 12:17:37 +02:00
|
|
|
## Options
|
2017-12-23 14:07:45 +01:00
|
|
|
|
|
|
|
```
|
2020-05-16 16:11:55 +02:00
|
|
|
-h, --help help for create
|
|
|
|
--no-obscure Force any passwords not to be obscured.
|
|
|
|
--obscure Force any passwords to be obscured.
|
2017-12-23 14:07:45 +01:00
|
|
|
```
|
|
|
|
|
2019-06-20 17:18:02 +02:00
|
|
|
See the [global flags page](/flags/) for global options not listed here.
|
|
|
|
|
2020-05-22 12:17:37 +02: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.
|
|
|
|
|