Lightroom Cloud Extension

This project extend Adobe Lightroom with cloud support making it possible to access a catalog from different machines safely without corrupting the catalog.

Features:

Have a catalog file in a shared location, such as a folder in Google Drive, Dropbox, or a NAS, and have lrcloud synchronize the catalog between a local and the shared location.
Only synchronizing the changes not the whole catalog
Support Smart Previews
On-the-fly catalog compression

Current limitations:

The paths in the shared catalog are not converted thus a catalog cannot be shared between Window and OSX.
No GUI
No simultaneous catalog access

Usage

$ python -m lrcloud -h
usage: __main__.py [-h] [--init-push-to-cloud | --init-pull-from-cloud]
                   [--cloud-catalog CLOUD_CATALOG]
                   [--local-catalog LOCAL_CATALOG]
                   [--lightroom-exec LIGHTROOM_EXEC | --lightroom-exec-debug LIGHTROOM_EXEC_DEBUG]
                   [-v] [--no-smart-previews] [--config-file CONFIG_FILE]
                   [--diff-cmd DIFF_CMD] [--patch-cmd PATCH_CMD]

Cloud extension to Lightroom

optional arguments:
  -h, --help            show this help message and exit
  --init-push-to-cloud  Initiate the local catalog and push it to the cloud
                        (default: False)
  --init-pull-from-cloud
                        Download the cloud catalog and initiate a
                        corresponding local catalog (default: False)
  --cloud-catalog CLOUD_CATALOG
                        The cloud/shared catalog file e.g. located in Google
                        Drive or Dropbox (default: None)
  --local-catalog LOCAL_CATALOG
                        The local Lightroom catalog file (default: None)
  --lightroom-exec LIGHTROOM_EXEC
                        The Lightroom executable file (default: None)
  --lightroom-exec-debug LIGHTROOM_EXEC_DEBUG
                        Instead of running Lightroom, append data to the end
                        of the catalog file (default: None)
  -v, --verbose         Increase output verbosity (default: False)
  --no-smart-previews   Don't Sync Smart Previews (default: False)
  --config-file CONFIG_FILE
                        Path to the configure (.ini) file (default:
                        /home/madsbk/.lrcloud.ini)
  --diff-cmd DIFF_CMD   The command that given two files, $in1 and $in2,
                        produces a diff file $out (default: ./jdiff -f $in1
                        $in2 $out)
  --patch-cmd PATCH_CMD
                        The command that given a file, $in1, and a path,
                        $patch, produces a file $out (default: ./jptch $in1
                        $patch $out)

Metadata

Release files for lrcloud 0.1.1.post4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lrcloud 0.1.1.post4
File	Size	Uploaded	Provenance
lrcloud-0.1.1.post4.tar.gz	21.9 kB	May 27, 2016	Without provenance	Details

Release files / lrcloud-0.1.1.post4.tar.gz

Download URL	lrcloud-0.1.1.post4.tar.gz
Size	21.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`5f8f15799c039fa6a08359aa317d8934e229a40628f26d09812b0aed0b5dc4fb`
BLAKE2b-256 checksum How to use checksums	`dda8902c5f412f88ff6999dbafcb0750cb503efce29ba4e02e368577ca88c166`
Upload date	May 27, 2016
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for lrcloud 0.1.1.post4

Report project as malware

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.