Skip to content


Subversion checkout URL

You can clone with
Download ZIP command-line (CLI) tools and software development kit (SDK) for Ruby.
Branch: master
Failed to load latest commit information.
bin Fixed some typos and improved the wording in the --help output.
doc Added a repository enumeration example to the README and to doc/examp…
spec Raise errors sent from the server instead of hard-coded print/exit
.gemspec Removed the unused sparql-client dependency.
.rvmrc Imported an RVM configuration file.
.yardopts Improved the project and gem title/description.
AUTHORS Ensured that the author list uses e-mail addresses.
CREDITS Added Gabriel Horner to the contributors list.
Gemfile Removed the unused sparql-client dependency.
Gemfile.lock Removed the unused sparql-client dependency.
README Created repository. Removed the unused sparql-client dependency.
Rakefile Fix a bug with rake version:bump on some git versions
UNLICENSE Created repository.
dydra.gemspec Renamed the gem to the correct name. Software Development Kit (SDK) for Ruby

This is the official command-line client (CLI) and Ruby software development kit (SDK) for, the cloud-hosted RDF & SPARQL database service.


Authenticating with API token

Dydra.authenticate!(:token => api_token)

Enumerating your repositories

account ='jhacker')
account.each do |repository|
  puts repository

Accessing a repository belonging to your account

account ='jhacker')
repository = account['foaf']



Note: the instructions in this README, and the operation of the library itself, implicitly assume a Unix system (Mac OS X, Linux, or *BSD) at present. Patches improving Windows support are most welcome.


The recommended installation method is via RubyGems. To install the latest official release of the SDK and CLI, do:

$ [sudo] gem install dydra

Should you wish to remove the SDK and CLI from your system, do:

$ [sudo] gem uninstall dydra



The first time you run the dydra command, you'll be asked to authenticate. When you type in your username and password, your API token will be fetched and stored in the the ~/.dydra/credentials file in your home directory, enabling you to bypass the authentication step for future commands.


Specifying the API token

Another way to specify the API token is to set the DYDRA_TOKEN environment variable, which takes precedence over any API token specified in the ~/.dydra/credentials file. This can be handy, for example, when executing a one-off command against another Dydra account you may have:

$ export DYDRA_TOKEN='R33l6sEnxiExJfOYnZHWs2v06yWd2FUiBZc874vTt6QUSPz96imMf48tqLsz'

Using a SOCKS proxy

The command-line client optionally supports using a SOCKS proxy to access To make use of this functionality, install the Socksify library for Ruby and set the SOCKS_SERVER environment variable to point to your local SOCKS proxy:

$ [sudo] gem install socksify
$ export SOCKS_SERVER=''


To get a local working copy of the development repository, do:

$ git clone git://

Mailing List




  • Do your best to adhere to the existing coding conventions and idioms.
  • Don't use hard tabs, and don't leave trailing whitespace on any line.
  • Do document every method you add using YARD annotations. Read the tutorial or just look at the existing code for examples.
  • Don't touch the .gemspec, VERSION, or AUTHORS files. If you need to change them, do so on your private branch only.
  • Do feel free to add yourself to the CREDITS file and the corresponding list in the README. Alphabetical order applies.


This is free and unencumbered public domain software. For more information, see or the accompanying {file:UNLICENSE} file.

Something went wrong with that request. Please try again.