Duke-GCB/bespin-ui

Name: bespin-ui

Owner: Duke Center for Genomic and Computational Biology

Description: An ember.js application frontend for bespin-api

Created: 2016-12-14 16:31:11.0

Updated: 2017-09-19 15:01:00.0

Pushed: 2017-12-14 19:19:39.0

Homepage:

Size: 917

Language: JavaScript

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Bespin-UI

An ember.js application frontend for bespin-api.

Prerequisites

You will need the following things properly installed on your computer.

• Git
• Node.js (with NPM)
• Ember CLI
• PhantomJS

Installation

• git clone git@github.com:Duke-GCB/bespin-ui.git this repository
• cd bespin-ui
• npm install

Running / Development

• Check the Bespin API endpoint configured in config/environment.js
• ember serve
• Visit your app at http://localhost:4200.

Running Tests

• ember test
• ember test --server

Manual Builds

• ember build (Local Development)
• JOB_WATCHER_URL="wss://bespin-ws.gcb.duke.edu" ember build --environment production (production) (see below)

Automated Releases

The npm version command triggers the automated release process using Travis-CI and GitHub. npm version takes care of creating a git tag using semantic versioning. It runs the preversion and postversion scripts specified in package.json before and after tagging the new version. These scripts ensure that releases happen from a clean and current master branch, passes tests, and pushes the resulting tag to GitHub. When the new tag is pushed, Travis-CI builds releases for it and uploads them back to GitHub as Downloads.

The following command is all that's needed to produce a release:

version patch

You can also use major or minor for different version increments, or customize the commit message with -m

Deployment Details

Our bespin-web ansible role creates a docker container from bespin-webapp-docker, with a specified release of bespin-ui.

For each release, Travis-CI creates release builds and uploads them to the tag's GitHub release (.travis.yml). One build, bespin-ui-prod.tar.gz is produced with the prod JOB_WATCHER_URL, and the other, bespin-ui-dev.tar.gz is produced with the dev JOB_WATCHER_URL. Both are optimized, minified production builds that are ready to be served. The bespin-webapp-docker container serves these files with Apache.

For a different JOB_WATCHER_URL, create a manual build (see build-release.sh for examples).