Directories created

The following directories are created:

  • ~/.selectiveshare - Workspace for sltv
  • ~/test_sync - Created by the example scripts for testing synchronisation.
    It can be changed in the script activate.
  • /usr/share/doc/sltv-client/example - Example scripts


The following applications need to be available in the path:

  • GPG
  • rdiff
  • SQLite

Copy the example scripts to a convenient location where they can be modified and executed from.


  1. Download the appropriate installer.
  2. Execute sudo apt-get install rdiff librsync1
  3. Execute sudo dpkg -i sltv-client_A.B.C.D_ARCH.deb


  1. Run register.

    The output should be:

     $ ./register
     Registering application

    This command will create the initial ~/.selectiveshare/ structure.

Create encryption key

  1. On the first machine:

    Run gen-key.

    IMPORTANT: Make a backup copy of the ~/.selectiveshare/keys/ directory after key generation is completed. You will need this if something happens to the .selectiveshare/ folder.

    The output should be:

     $ gen-key 
     Generating key for user Selective Share
     gpg: Generating key
  2. On the following machines:

    Copy the ~/.selectiveshare/keys/ folder from the first PC into the .selectiveshare/ folder of the current PC.

    If the keys folders of different PCs mismatch, they won’t be able to synchronise to each other. Support for multiple keys is not yet implemented.


  1. Run activate.

    The output should be:

     $ ./activate  
     Synchronise this folder ...   
     ... using this name as reference
  2. Update the synchronise script with you login details and encryption credentials.
  3. Run synchronise.

    The output should be:

    Synchronising folders for testapp
     <INFO> [20:07:30] common common.lisp (verify-environment) -
      Using keys at '/home/USERNAME/.selectiveshare/keys/' for GPG-USER
     <INFO> [20:07:30] director director.lisp (sync-folders) -
      Using URL
     <INFO> [20:07:30] director director.lisp (sync-folders) -
      Data store is at /home/USERNAME/.selectiveshare/stores/testapp/
    <DEBUG> [20:07:30] director director.lisp (sync-folders) - Sync'ing folders:
      (syncfolder /home/USERNAME/test_sync/)
    . . .
  4. Inspect the log files at ~/.selectiveshare/log/ and ~/.selectiveshare/stores/testapp/log/. They should indicate a successfull synchronisation process.

Next steps:

  • Repeat the register and activate steps on a different machine. Copy the ~/.selectiveshare/keys folder to each synchronised machine instead of creating new keys.
  • Create files in the test_sync folder and run the synchronise script to synchronise between PCs.


The gen-key script generates a new encryption key and replaces the existing one. Do not run this script once the synchronise script was run. It will prevent previously synchronised data from being decrypted.

The register script registers an application for synchronisation services. A single registered application can have multiple associated directories. All the associated directories are synchronised simultaneously.

The activate script associates a directory with a registered application using a name as reference. The same directory content (ie same reference name) can have different directory names on different machines.

The synchronise scrypt synchronises all the directories associated with the specified application. It requires the GPG passphrase used during key generation and the account credentials used to create the web account.


sltv -h displays all the available commands.

Command specific help is obtained via sltv help COMMAND.


Log files are stored in ~/.selectiveshare/stores/testapp/log/ and ~/.selectiveshare/log/.

Authentication failure can happen for the following reasons:

  • Wrong credentials specified in synchronise.
  • Server problems.

Please send an email if you suspect it is server problems.

If synchronisation fails because of decryption problems it usually means that a new GPG key was generated after previously synchronising using a different key. Ensure that ~/.selectiveshare/keys/ contains the correct key. Please request help if the problem can’t be resolved.


Please use the support forum for questions and comments.