[
OneDataShare is a cloud-hosted data transfer tool that manages and optimizes the movement of data across arbitrary endpoints in a protocol-agnostic manner. OneDataShare also provides APIs for browsing and managing data on remote endpoints, as well as both command line and browser clients for interacting with the system.
Clients submit jobs to a OneDataShare server and the OneDataShare server performs the transfer when resources permit. The OneDataShare server responds to any failures that may occur during transfer automatically, handling them in an appropriate way when possible and informing the user if a job cannot be completed.
Building OneDataShare requires a Java SE 7 compatible runtime (JRE) and development kit (JDK) to be installed.
Building is as simple as running make.
Additional build targets can be viewed by running make help.
The OneDataShare configuration file (stork.conf) can be used to change settings for the server and client tools. The search order for the configuration file is as follows:
- $STORK_CONFIG
- ~/.stork.conf
- /etc/stork.conf
- $STORK/stork.conf
- /usr/local/stork/stork.conf
- stork.conf in currect directory
Even if the file cannot be found automatically, every valid config variable has a default value. The Stork server will issue a warning on startup if a config file cannot be found.
bin/— Contains scripts to execute JARs. This directory gets included in the release tarfile for a binary release.build/— Gets created when the project is built. Contains all class files generated by the Java compiler. Everything in here then gets put into stork.jar after building.doc/— Contains documentation after runningmake doc.lib/— Contains external libraries that get included in stork.jar on build.libexec/— Stork searches here for transfer module binaries when it is run. Gets included in the binary release tarfile.stork/— Includes all the Java source files for Stork.web/— Includes static web files for the browser client.