![]() This commit changes a way we load accounts for profile view: * instead of using several views with profile controllers, always use one view to render hooks. This is achieved by redirecting to individual account page from main profile page (for example when going into /profile as a user drogus, the effective address will be /profile/drogus) * instead of using observers to wait for accounts to load I just use promise in ProfileRoute#model which effectively ensures that accounts are loaded at the time we want to select an individual account * profile controller is split into profile and account controller |
||
---|---|---|
assets | ||
config | ||
lib | ||
locales | ||
play | ||
public | ||
script | ||
spec | ||
.buildpacks | ||
.gitignore | ||
.rspec | ||
.slugignore | ||
.travis.yml | ||
Assetfile | ||
config.ru | ||
CONTRIBUTING.md | ||
Gemfile | ||
Gemfile.lock | ||
Guardfile | ||
Guardfile.phantom | ||
LICENSE | ||
NOTES.txt | ||
Procfile | ||
Rakefile | ||
README.md | ||
run_qunit.js | ||
seeds.sql | ||
travis-web.gemspec |
Travis CI ember web client
Running the app
In order to run the app you need to install dependencies with:
bundle install
Then you have to run the server, the easiest way to do this is to use foreman:
bundle exec foreman start
Now you can open localhost:5000
By default it uses the official API at https://api.travis-ci.org
, but you
can customize the API server URL using:
API_ENDPOINT="http://localhost:3000/" bundle exec foreman start
This will run against API run locally.
Compiling assets manually
bundle exec rakep
ENV=production bundle exec rakep
Running the spec suite
First, start the app (see above).
bundle exec foreman start
To run the Ruby specs, run rspec against the spec/ directory:
bundle exec rspec spec/
To run the Jasmine specs, open the spec page: localhost:5000/spec.html
i18n
Localization for travis-web is managed via localeapp. If you are interested in improving the existing localizations or adding a new locale, please contact us on irc (#travis) and we will set you up.
Please do not edit the YAML files directly.
Localization data can be synced with the following rake task:
bundle exec localeapp:update
This will publish any new keys in en.yml, as well as any missing keys from your handlebars templates and pull down the latest localizations.
note: You will need to have the localeapp api key exported to LOCALEAPP_API_KEY