The Ember web client for Travis CI
![]() After change log rendering method, to append HTML elements instead of rerendering the entire thing, the case of gradual rendering of a log started to behave much better (because we just append new elements), but the initial render took a bit longer, because of the fact that appending large separate HTML elements to DOM at once is not a good idea. In order to make the situation better I added simple optimization. Elements are added to DocumentFragment node before inserting to DOM and appended to DOM only after all elements are processed. That way, when log needs to be rendered all at once, we will not do any DOM operations until log is ready. |
||
---|---|---|
.localeapp | ||
assets | ||
config | ||
lib | ||
locales | ||
play | ||
public | ||
script | ||
spec | ||
.buildpacks | ||
.gitignore | ||
.rspec | ||
.slugignore | ||
.travis.yml | ||
Assetfile | ||
config.ru | ||
Gemfile | ||
Gemfile.lock | ||
Guardfile | ||
Guardfile.phantom | ||
LICENCSE | ||
NOTES.txt | ||
Procfile | ||
Rakefile | ||
README.md | ||
run_jasmine.coffee | ||
run_mocha.js | ||
seeds.sql | ||
travis-web.gemspec |
Travis CI ember web client
Running the app
This is a static html/js app so you shouldn't need to install anything.
git clone git://github.com/travis-ci/travis-web.git
cd travis-web
open public/index.html
Running locally with a local API server:
RUN_API=1 bundle exec rackup -p 3000
Running against existing API endpoint:
API_ENDPOINT="https://api.travis-ci.org/" RUN_API=0 bundle exec rackup
Run locally, one on ci.dev
and one on api.dev
:
. dev.env
bundle exec rackup
Compiling assets manually
bundle exec rakep
ENV=production bundle exec rakep
Compiling assets on change
bundle exec guard