Stable releases of BioBlend are best installed via
PyPI using something like:
$ pip install bioblend
Alternatively, you may install the most current source code from our Git repository, or fork the project on Github. To install from source, do the following:
# Clone the repository to a local directory $ git clone https://github.com/galaxyproject/bioblend.git # Install the library $ cd bioblend $ python setup.py install
After installing the library, you will be able to simply import it into your
Python environment with
import bioblend. For details on the available functionality,
see the API documentation.
BioBlend requires a number of Python libraries. These libraries are installed
automatically when BioBlend itself is installed, regardless whether it is installed
via PyPi or by running
python setup.py install command. The current list of
required libraries is always available from setup.py in the source code
If you also want to run tests locally, some extra libraries are required. To install them, run:
$ python setup.py test
To get started using BioBlend, install the library as described above. Once the library becomes available on the given system, it can be developed against. The developed scripts do not need to reside in any particular location on the system.
It is probably best to take a look at the example scripts in
directory and browse the API documentation. Beyond that, it's up to your creativity :).
Anyone interested in contributing or tweaking the library is more then welcome to do so. To start, simply fork the Git repository on Github and start playing with it. Then, issue pull requests.
BioBlend's API focuses around and matches the services it wraps. Thus, there are two top-level sets of APIs, each corresponding to a separate service and a corresponding step in the automation process. Note that each of the service APIs can be used completely independently of one another.
Effort has been made to keep the structure and naming of those API's consistent across the library but because they do bridge different services, some discrepancies may exist. Feel free to point those out and/or provide fixes.
For Galaxy, an alternative :ref:`object-oriented API <objects-api>` is also available. This API provides an explicit modeling of server-side Galaxy instances and their relationships, providing higher-level methods to perform operations such as retrieving all datasets for a given history, etc. Note that, at the moment, the oo API is still incomplete, providing access to a more restricted set of Galaxy modules with respect to the standard one.
API used to manipulate the instantiated infrastructure. For example, scale the size of the compute cluster, get infrastructure status, get service status.
.. toctree:: :maxdepth: 2 :glob: api_docs/cloudman/*
API used to manipulate genomic analyses within Galaxy, including data management and workflow execution.
.. toctree:: :maxdepth: 3 :glob: api_docs/galaxy/*
API used to interact with the Galaxy Toolshed, including repository management.
.. toctree:: :maxdepth: 3 :glob: api_docs/toolshed/*
BioBlend allows library-wide configuration to be set in external files. These configuration files can be used to specify access keys, for example.
.. toctree:: :maxdepth: 1 :glob: api_docs/lib_config
If you'd like to do more than just a mock test, you'll want to point BioBlend to an instance of Galaxy. Do so by exporting the following two variables:
$ export BIOBLEND_GALAXY_URL=http://127.0.0.1:8080 $ export BIOBLEND_GALAXY_API_KEY=<API key>
The unit tests, stored in the
tests folder, can be run using
nose. From the project root:
If you've run into issues, found a bug, or can't seem to find an answer to your question regarding the use and functionality of BioBlend, please use Github Issues page to ask your question.
Links to other documentation and libraries relevant to this library: