github.com/ncw/rclone@v1.48.1-0.20190724201158-a35aa1360e3e/docs/content/jottacloud.md (about)

     1  ---
     2  title: "Jottacloud"
     3  description: "Rclone docs for Jottacloud"
     4  date: "2018-08-07"
     5  ---
     6  
     7  <i class="fa fa-archive"></i> Jottacloud
     8  -----------------------------------------
     9  
    10  Paths are specified as `remote:path`
    11  
    12  Paths may be as deep as required, eg `remote:directory/subdirectory`.
    13  
    14  To configure Jottacloud you will need to enter your username and password and select a mountpoint.
    15  
    16  Here is an example of how to make a remote called `remote`.  First run:
    17  
    18       rclone config
    19  
    20  This will guide you through an interactive setup process:
    21  
    22  ```
    23  No remotes found - make a new one
    24  n) New remote
    25  s) Set configuration password
    26  q) Quit config
    27  n/s/q> n
    28  name> jotta
    29  Type of storage to configure.
    30  Enter a string value. Press Enter for the default ("").
    31  Choose a number from below, or type in your own value
    32  [snip]
    33  14 / JottaCloud
    34     \ "jottacloud"
    35  [snip]
    36  Storage> jottacloud
    37  ** See help for jottacloud backend at: https://rclone.org/jottacloud/ **
    38  
    39  User Name:
    40  Enter a string value. Press Enter for the default ("").
    41  user> user@email.tld
    42  Edit advanced config? (y/n)
    43  y) Yes
    44  n) No
    45  y/n> n
    46  Remote config
    47  
    48  Do you want to create a machine specific API key?
    49  
    50  Rclone has it's own Jottacloud API KEY which works fine as long as one only uses rclone on a single machine. When you want to use rclone with this account on more than one machine it's recommended to create a machine specific API key. These keys can NOT be shared between machines.
    51  
    52  y) Yes
    53  n) No
    54  y/n> y
    55  Your Jottacloud password is only required during setup and will not be stored.
    56  password:
    57  
    58  Do you want to use a non standard device/mountpoint e.g. for accessing files uploaded using the official Jottacloud client?
    59  
    60  y) Yes
    61  n) No
    62  y/n> y
    63  Please select the device to use. Normally this will be Jotta
    64  Choose a number from below, or type in an existing value
    65   1 > DESKTOP-3H31129
    66   2 > test1
    67   3 > Jotta
    68  Devices> 3
    69  Please select the mountpoint to user. Normally this will be Archive
    70  Choose a number from below, or type in an existing value
    71   1 > Archive
    72   2 > Shared
    73   3 > Sync
    74  Mountpoints> 1
    75  --------------------
    76  [jotta]
    77  type = jottacloud
    78  user = 0xC4KE@gmail.com
    79  client_id = .....
    80  client_secret = ........
    81  token = {........}
    82  device = Jotta
    83  mountpoint = Archive
    84  --------------------
    85  y) Yes this is OK
    86  e) Edit this remote
    87  d) Delete this remote
    88  y/e/d> y
    89  ```
    90  Once configured you can then use `rclone` like this,
    91  
    92  List directories in top level of your Jottacloud
    93  
    94      rclone lsd remote:
    95  
    96  List all the files in your Jottacloud
    97  
    98      rclone ls remote:
    99  
   100  To copy a local directory to an Jottacloud directory called backup
   101  
   102      rclone copy /home/source remote:backup
   103  
   104  ### Devices and Mountpoints ###
   105  
   106  The official Jottacloud client registers a device for each computer you install it on and then creates a mountpoint for each folder you select for Backup.
   107  The web interface uses a special device called Jotta for the Archive, Sync and Shared mountpoints. In most cases you'll want to use the Jotta/Archive device/mounpoint however if you want to access files uploaded by the official rclone provides the option to select other devices and mountpoints during config.
   108  
   109  ### --fast-list ###
   110  
   111  This remote supports `--fast-list` which allows you to use fewer
   112  transactions in exchange for more memory. See the [rclone
   113  docs](/docs/#fast-list) for more details.
   114  
   115  Note that the implementation in Jottacloud always uses only a single
   116  API request to get the entire list, so for large folders this could
   117  lead to long wait time before the first results are shown.
   118  
   119  ### Modified time and hashes ###
   120  
   121  Jottacloud allows modification times to be set on objects accurate to 1
   122  second.  These will be used to detect whether objects need syncing or
   123  not.
   124  
   125  Jottacloud supports MD5 type hashes, so you can use the `--checksum`
   126  flag.
   127  
   128  Note that Jottacloud requires the MD5 hash before upload so if the
   129  source does not have an MD5 checksum then the file will be cached
   130  temporarily on disk (wherever the `TMPDIR` environment variable points
   131  to) before it is uploaded.  Small files will be cached in memory - see
   132  the `--jottacloud-md5-memory-limit` flag.
   133  
   134  ### Deleting files ###
   135  
   136  By default rclone will send all files to the trash when deleting files.
   137  Due to a lack of API documentation emptying the trash is currently
   138  only possible via the Jottacloud website. If deleting permanently
   139  is required then use the `--jottacloud-hard-delete` flag,
   140  or set the equivalent environment variable.
   141  
   142  ### Versions ###
   143  
   144  Jottacloud supports file versioning. When rclone uploads a new version of a file it creates a new version of it. Currently rclone only supports retrieving the current version but older versions can be accessed via the Jottacloud Website.
   145  
   146  ### Quota information ###
   147  
   148  To view your current quota you can use the `rclone about remote:`
   149  command which will display your usage limit (unless it is unlimited)
   150  and the current usage.
   151  
   152  ### Device IDs ###
   153  
   154  Jottacloud requires each 'device' to be registered. Rclone brings such a registration to easily access your account but if you want to use Jottacloud together with rclone on multiple machines you NEED to create a seperate deviceID/deviceSecrect on each machine. You will asked during setting up the remote. Please be aware that this also means that copying the rclone config from one machine to another does NOT work with Jottacloud accounts. You have to create it on each machine.
   155  
   156  <!--- autogenerated options start - DO NOT EDIT, instead edit fs.RegInfo in backend/jottacloud/jottacloud.go then run make backenddocs -->
   157  ### Standard Options
   158  
   159  Here are the standard options specific to jottacloud (JottaCloud).
   160  
   161  #### --jottacloud-user
   162  
   163  User Name:
   164  
   165  - Config:      user
   166  - Env Var:     RCLONE_JOTTACLOUD_USER
   167  - Type:        string
   168  - Default:     ""
   169  
   170  ### Advanced Options
   171  
   172  Here are the advanced options specific to jottacloud (JottaCloud).
   173  
   174  #### --jottacloud-md5-memory-limit
   175  
   176  Files bigger than this will be cached on disk to calculate the MD5 if required.
   177  
   178  - Config:      md5_memory_limit
   179  - Env Var:     RCLONE_JOTTACLOUD_MD5_MEMORY_LIMIT
   180  - Type:        SizeSuffix
   181  - Default:     10M
   182  
   183  #### --jottacloud-hard-delete
   184  
   185  Delete files permanently rather than putting them into the trash.
   186  
   187  - Config:      hard_delete
   188  - Env Var:     RCLONE_JOTTACLOUD_HARD_DELETE
   189  - Type:        bool
   190  - Default:     false
   191  
   192  #### --jottacloud-unlink
   193  
   194  Remove existing public link to file/folder with link command rather than creating.
   195  Default is false, meaning link command will create or retrieve public link.
   196  
   197  - Config:      unlink
   198  - Env Var:     RCLONE_JOTTACLOUD_UNLINK
   199  - Type:        bool
   200  - Default:     false
   201  
   202  #### --jottacloud-upload-resume-limit
   203  
   204  Files bigger than this can be resumed if the upload fail's.
   205  
   206  - Config:      upload_resume_limit
   207  - Env Var:     RCLONE_JOTTACLOUD_UPLOAD_RESUME_LIMIT
   208  - Type:        SizeSuffix
   209  - Default:     10M
   210  
   211  <!--- autogenerated options stop -->
   212  
   213  ### Limitations ###
   214  
   215  Note that Jottacloud is case insensitive so you can't have a file called
   216  "Hello.doc" and one called "hello.doc".
   217  
   218  There are quite a few characters that can't be in Jottacloud file names. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a ? in it will be mapped to ? instead.
   219  
   220  Jottacloud only supports filenames up to 255 characters in length.
   221  
   222  ### Troubleshooting ###
   223  
   224  Jottacloud exhibits some inconsistent behaviours regarding deleted files and folders which may cause Copy, Move and DirMove operations to previously deleted paths to fail. Emptying the trash should help in such cases.