Google Git
Sign in
apache / incubator-taverna-databundle-viewer / d5876781485290f2b6a17e76ce3c1aca60ae8b74
commitd5876781485290f2b6a17e76ce3c1aca60ae8b74[log] [tgz]
authorDenis Karyakin <samhane.me@gmail.com>Tue Aug 18 17:36:55 2015 +0300
committerDenis Karyakin <samhane.me@gmail.com>Tue Aug 18 17:36:55 2015 +0300
tree9dbfc9b13af531ad4993f2e79bc7a3c7b609e115
parentb189da8685b47a7dbba4ae8ffae34c79a438e72c [diff]
Add ruby and nodejs buildpacks for heroku
1 file changed
tree: 9dbfc9b13af531ad4993f2e79bc7a3c7b609e115
  1. app/
  2. bin/
  3. config/
  4. db/
  5. lib/
  6. log/
  7. public/
  8. spec/
  9. vendor/
  10. .buildpacks
  11. .env.example
  12. .gitignore
  13. .rspec
  14. .ruby-gemset
  15. .ruby-version
  16. bower.json
  17. config.ru
  18. GEM_LICENSES.md
  19. Gemfile
  20. Gemfile.lock
  21. LICENSE
  22. NOTICE
  23. Procfile
  24. Rakefile
  25. README.md
README.md

Apache Taverna Databundle Viewer

Code Climate Test Coverage Build Status

Apache Taverna Databundle Viewer is planned as a web interface for displaying Taverna databundles (workflow inputs/outputs/run), as produced by the Apache Taverna workflow system.

This module is work in progress as part of Google Summer of Code 2015.

You can see working prototype there: DataBundleViewer

License

(c) 2015 Apache Software Foundation

This product includes software developed at The Apache Software Foundation.

Licensed under the Apache License 2.0, see the file LICENSE for details.

The file NOTICE contain any additional attributions and details about embedded third-party libraries and source code.

Contribute

Please subscribe to and contact the [dev@taverna](http://taverna.incubator.apache.org/community/lists#dev mailing list) for any questions, suggestions and discussions about the Apache Taverna Databundle Viewer.

Bugs and feature plannings are tracked in the Jira Issue tracker under the TAVERNA component GSOC Taverna Databundle Viewer. Feel free to add an issue!

To suggest changes to this source code, feel free to raise a GitHub pull request. Any contributions received are assumed to be covered by the Apache License 2.0. We might ask you to sign a Contributor License Agreement before accepting a larger contribution.

Building and install requirements

Requirements

Set up

  1. Run bin/setup to install dependencies, create and set up database. By default used PostgreSQL
  2. Run rake bower:install to install front-end assets

Set up omniauth

Google omniauth:

  1. Visit Console google. Click by link APIs & auth -> Credentials -> Create new Client ID
  2. Set Redirect URIs as http://yoursite.com/users/auth/google_oauth2/callback
  3. Enable Google+ API. Click by link APIs & auth -> Google+ API -> Enable API
  4. Set up environmental variables GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET

Facebook omniauth:

  1. Visit Developers Facebook
  2. Click by My Apps -> Add a New App
  3. Visit Settings -> Advanced. Fill in field Valid OAuth redirect URIs with http://yoursite.com/users/auth/facebook/callback
  4. Set up environmental variables FACEBOOK_CLIENT_ID, FACEBOOK_CLIENT_SECRET

Set up the AWS S3 for storage files in production environment

  1. Visit AWS Console
  2. Open the Amazon S3 console.
  3. Click Create Bucket.
  4. In the Create a Bucket dialog box enter a name and select a region.
  5. Click on the name of your account (it is located in the top right corner of the console). Then, in the expanded drop-down list, select Security Credentials.
  6. Click the Get Started with IAM Users button.
  7. Click the Create New Users
  8. Enter User Name(s) and click the Create
  9. Click the Download Credentials
  10. Set up environmental variables S3_KEY, S3_SECRET, S3_REGION, S3_ASSET_URL, S3_BUCKET_NAME

Ways to set up environmental variables

  1. Set Unix Environment Variables
  2. Use a local .env file. Template you can find in .env.example file
  3. Set environmental variables as parameters to command rails s

Don't forget: Keeping Environment Variables Private

Usage

Run server with command rails s

TODO

  • ...

Documentation

TODO

  • ...