The SSH provider enables commits to be stored on any server where the user has remote access over SSH. The URI syntax is:
path is interpreted as an absolute path unless it starts with
The SSH provider uses rsync to copy files to subdirectories within the path,
with metadata being stored in a
metadata.json file. This means that pushes
are always full sends, as titan is sending data to a newly created directory.
Pulls, on the other hand, may not need to transfer all data depending on what
state exists locally.
The system must have
sudo installed and the user must have
privileges for running rsync. This enables file ownership and permissions to be
password is not specified, then the user will be prompted for a password
at the time they do the push or pull operation. Users are also able to use a
keyFile instead of a password:
ssh://user@host[:port]/path -p keyfile=/path/to/keyFile
Like the S3 provider, the SSH provider has inherent scalability limitations. For example, finding the latest commit requires listing all commits in the path, reading the metadata file for each, and comparing the result. It should only be used for storing relatively small numbers of commits. Improving this will require a new provider that includes a robust metadata layer on top of the base SSH functionality.
SSH Specific Parameters¶
keyFile=/path/to/keyFile Location of private SSH key file
The SSH connection is made from within the Titan server container, so the host
name must be resolvable from within the container. In general, this should
not be an issue because it runs within the host’s network namespace, but
there are exceptions, such as specifying
localhost won’t work properly.
If you’re trying to diagnose a connectivity problem that works from
the host system but not within titan, you can run
docker exec -it titan-server /bin/bash and run standard Linux commands
(such as ssh and ping) to debug the issue.