This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
DEPRECATED
========

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="">`__.
Release History

Release History

0.3.1-1

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.3.0-2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.3.0-1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.5-1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2-1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1-1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1a-1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
jottacloudclient-0.3.1-1.tar.gz (30.1 kB) Copy SHA256 Checksum SHA256 Source Aug 26, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting