SequenceServer lets you rapidly set up a BLAST+ server with an intuitive user interface for personal or group use.
If you use SequenceServer, please cite:
For installation instructions and how to use SequenceServer please see https://sequenceserver.com/
If you want to run SequenceServer directly from source code, please see 'Develop and contribute' section below.
New releases are announced on GitHub release page and on Google Group, while our GitHub project board provides an overview of ongoing development efforts.
(Read about extensive testing of SequenceServer 2.0 candidate releases by the community: https://groups.google.com/d/msg/sequenceserver/c98ePBzcuVE/lN-S35jVHgAJ.)
Please report any issues here: https://github.com/wurmlab/sequenceserver/issues
To develop and contribute, you will need to run SequenceServer from source (see below).
You will need Ruby and RubyGems:
# Install bundler gem to install Ruby dependencies
gem install bundler
# Move to where you downloaded or cloned seqserv
cd sequenceserver
# Use bundler to install Ruby dependencies
bundle install
# Use bundler to run SequenceServer
bundle exec bin/sequenceserver
If you do not plan to develop, you can skip installing development dependencies
by running bundle install --without=development.
During development, you should use -D option to run SequenceServer in development mode. In this mode, SequenceServer logs verbosely and uses raw front-end files.
# Run SequenceServer in development mode
bundle exec bin/sequenceserver -D
You will need Node and npm if you want to modify and build frontend code:
# Install frontend dependencies
npm install
# Build minified JS and CSS bundles
npm run-script build
Or if you are using docker, you can build the frontend code and include it in the image by specifying '--target=minify' to the docker build command:
docker build . -t seqserv-with-customisations --target=minify
We use RSpec and Capybara for testing. Our test suite covers 87% of the codebase. Tests are run automatically when you open a pull-request (see Getting code merged section below) but it may be desirable sometimes to run a single test, whole file, or all tests locally:
To run a single test (a.k.a, scenario):
bundle exec rspec spec/foo_spec.rb -e 'bar'
To run all tests in a single file:
bundle exec rspec spec/foo_spec.rb
To run all tests:
bundle exec rspec
We use CodeClimate for static code analysis. CodeClimate is run automatically when you open a pull-request (see Getting code merged section below) but it may be desirable sometimes to run it locally.
For this, first install CodeClimate following the instructions at https://github.com/codeclimate/codeclimate.
Once CodeClimate is installed, install the required codeclimate 'engines':
codeclimate engines:install
To run all the style checkers:
codeclimate analyze
To run eslint:
codeclimate analyze -e eslint
To run rubocop:
codeclimate analyze -e rubocop
stylelint is used for CSS:
codeclimate analyze -e stylelint
The above commands respect the respective style checker's config files, e.g., .rubocopy.yml for Rubocop and so on.
Please open a pull-request on GitHub to get code merged. Our test suite and the CodeClimate static code analysis system will be automatically run on your pull-request. These should pass for your code to be merged. If you want to add a new feature to SequenceServer, please also add tests. In addition, code should be rubocop and eslint compliant, and hard-wrapped to 80 chars per line.
If you change frontend code (JavaScript and CSS), please build (i.e., minify and compress) and commit the resulting JS and CSS bundles before opening a pull-request. This is because SequenceServer is run in production mode by the test suite.
- Anurag Priyam (architect) - email | @yeban
- Yannick Wurm (PI) - email | @yannick__
- Mailing list / forum