========
As of 2016-01-01, this package is deprecated, and all code and scripts is merged into `jottalib`. So go get that one.
JOTTA CLOUD CLIENT
==================
A cli friendly sync client for `JottaCloud <http://jottacloud.com>`__.
It will sync your directory tree with JottaCloud, just like the official
client.
**Note. This a third-party, not an official client.**
Is it safe?
-----------
Being based on a reverse engineering of the protocol, things may break
in unexpected ways. *Don't rely on this as your sole backup* unless you
manually verify that the data is correctly transferred. **The authors
won't be held responsible for any data loss.**
How to get it
-------------
Run
::
pip install jottacloudclient
How to use it
-------------
Run ``jottacloudclientscanner.py`` at some interval:
::
python jottacloudclientscanner.py <top dir of your local tree> <the mount point on jottacloud>
The *top dir* is just an existing directory on your system that you want
to backup.
The *mount point* is a path on JottaCloud. It's put together from a
combination of **an existing device name**, **an existing backupdir**
and **a folder name** (that will be created if it doesn't exist). Like
this: ``/<devicename>/<backupdir>/<foldername>``
Example:
::
python jottacloudclientscanner.py /mnt/pictures /mybox/backup/pictures
How it works
~~~~~~~~~~~~
The basic operation on the JottaCloud servers is to *make file level
backups*. Unlike data-level protocols like ``rsync``, the JottaCloud
protocol does not seem to support `delta
encoding <http://en.wikipedia.org/wiki/Delta_encoding>`__, so file
syncing needs to happen by copying the full file content.
To determine if a file needs to be updated, **Jotta Cloud Client** will
compare the `md5 hash <http://en.wikipedia.org/wiki/MD5>`__ of the local
file with the one that the JottaCloud server reports. If the hashes
differ, the client will upload the file. This is akin to how the
official JottaCloud client works.
Setup
-----
The program needs to know your password to JottaCloud. There are two
ways to do this.
.netrc
~~~~~~
Create a ``$HOME/.netrc`` file with this entry:
::
machine jottacloud
login <yourusername>
password <yourpassword>
Make sure noone else can see it: ``chmod 0600 $HOME/.netrc``.
environment variables
~~~~~~~~~~~~~~~~~~~~~
Add ``JOTTACLOUD_USERNAME`` AND ``JOTTACLOUD_PASSWORD`` as variables in
the running environment:
::
export JOTTACLOUD_USERNAME=<username> JOTTACLOUD_PASSWORD=<password>
But it's not finished!
======================
But it's not very advanced!
===========================
Geez, you should've added *super bright idea* already!
======================================================
Want to help out? Read the HACKING.md document and get cracking!
Send pull requests to `the git
tree <https://gitorious.org/jottafs/jottacloudclient/>`__ or `start
fleshing out details in a bug
report <https://github.com/havardgulldahl/jottalib/issues/new>`__.
Metadata
Release files for jottacloudclient 0.3.1-1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jottacloudclient-0.3.1-1.tar.gz | 30.1 kB | Without provenance | Details for jottacloudclient-0.3.1-1.tar.gz |
Release files / jottacloudclient-0.3.1-1.tar.gz
| Download URL | jottacloudclient-0.3.1-1.tar.gz |
|---|---|
| Size | 30.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d17611929e86c77a5ebd7579cd95b0a7893770105cad6ce673223f6060f9e2b6
|
|
BLAKE2b-256 checksum How to use checksums |
f4026f170f0f6e5321bcd49905eb8b9271fff76d031ed2f7881ceb1da8ebb4c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jottacloudclient 0.3.1-1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.