Gecko [ www.utparral.edu.mx ]

Name	Size	Permission
__pycache__	[ DIR ]	drwxr-xr-x
pyrax_identity	[ DIR ]	drwxr-xr-x
adbackend.py	16.98 KB	-rw-r--r--
azurebackend.py	5.47 KB	-rw-r--r--
b2backend.py	8.82 KB	-rw-r--r--
_boto_multi.py	9.72 KB	-rw-r--r--
_boto_single.py	14.65 KB	-rw-r--r--
boxbackend.py	6.99 KB	-rw-r--r--
cfbackend.py	1.13 KB	-rw-r--r--
_cf_cloudfiles.py	3.85 KB	-rw-r--r--
_cf_pyrax.py	5.12 KB	-rw-r--r--
dpbxbackend.py	19.93 KB	-rw-r--r--
gdocsbackend.py	9.17 KB	-rw-r--r--
gdrivebackend.py	15.45 KB	-rw-r--r--
giobackend.py	8.05 KB	-rw-r--r--
hsibackend.py	2.67 KB	-rw-r--r--
hubicbackend.py	2.38 KB	-rw-r--r--
idrivedbackend.py	19.08 KB	-rw-r--r--
imapbackend.py	9.96 KB	-rw-r--r--
__init__.py	1.09 KB	-rw-r--r--
jottacloudbackend.py	5.54 KB	-rw-r--r--
lftpbackend.py	9.79 KB	-rw-r--r--
localbackend.py	2.96 KB	-rw-r--r--
mediafirebackend.py	4.71 KB	-rw-r--r--
megabackend.py	6.73 KB	-rw-r--r--
megav2backend.py	8.63 KB	-rw-r--r--
megav3backend.py	10.11 KB	-rw-r--r--
multibackend.py	15.49 KB	-rw-r--r--
ncftpbackend.py	5.58 KB	-rw-r--r--
onedrivebackend.py	15.03 KB	-rw-r--r--
par2backend.py	9.06 KB	-rw-r--r--
pcabackend.py	12.36 KB	-rw-r--r--
pydrivebackend.py	13.08 KB	-rw-r--r--
rclonebackend.py	4.22 KB	-rw-r--r--
README	2.52 KB	-rw-r--r--
rsyncbackend.py	6.51 KB	-rw-r--r--
s3_boto3_backend.py	9.41 KB	-rw-r--r--
s3_boto_backend.py	1.5 KB	-rw-r--r--
ssh_paramiko_backend.py	19.86 KB	-rw-r--r--
ssh_pexpect_backend.py	12.92 KB	-rw-r--r--
swiftbackend.py	10.04 KB	-rw-r--r--
sxbackend.py	2.31 KB	-rw-r--r--
tahoebackend.py	2.58 KB	-rw-r--r--
webdavbackend.py	19.77 KB	-rw-r--r--

Code Editor : README

= How to write a backend, in five easy steps! =

There are five main methods you want to implement:

__init__  - Initial setup
_get
 - Get one file
 - Retried if an exception is thrown
_put
 - Upload one file
 - Retried if an exception is thrown
_list
 - List all files in the backend
 - Return a list of filenames
 - Retried if an exception is thrown
_delete
 - Delete one file
 - Retried if an exception is thrown

There are other methods you may optionally implement:

_delete_list
 - Delete list of files
 - This is used in preference of _delete if defined
 - Must gracefully handle individual file errors itself
 - Retried if an exception is thrown
_query
 - Query metadata of one file
 - Return a dict with a 'size' key, and a file size value (-1 for not found)
 - Retried if an exception is thrown
_query_list
 - Query metadata of a list of files
 - Return a dict of filenames mapping to a dict with a 'size' key,
   and a file size value (-1 for not found)
 - This is used in preference of _query if defined
 - Must gracefully handle individual file errors itself
 - Retried if an exception is thrown
_retry_cleanup
 - If the backend wants to do any bookkeeping or connection resetting inbetween
   retries, do it here.
_error_code
 - Passed an exception thrown by your backend, return a log.ErrorCode that
   corresponds to that exception
_move
 - If your backend can more optimally move a local file into its backend,
   implement this.  If it's not implemented or returns False, _put will be
   called instead (and duplicity will delete the source file after).
 - Retried if an exception is thrown
_close
 - If your backend needs to clean up after itself, do that here.

== Subclassing ==

Always subclass from duplicity.backend.Backend

== Registering ==

You can register your class as a single backend like so:

duplicity.backend.register_backend("foo", FooBackend)

This will allow a URL like so: foo://hostname/path

Or you can register your class as a meta backend like so:
duplicity.backend.register_backend_prefix("bar", BarBackend)

Which will allow a URL like so: bar+foo://hostname/path and your class will
be passed the inner URL to either interpret how you like or create a new
inner backend instance with duplicity.backend.get_backend_object(url).

== Naming ==

Any method that duplicity calls will start with one underscore.  Please use
zero or two underscores in your method names to avoid conflicts.

== Testing ==

Use "./testing/manual/backendtest foo://hostname/path" to test your new
backend.  It will load your backend from your current branch.

${this.title}

Code Editor : README