This folder contains the source for the client application displaying information about the 'Connected Car'. It's built with Ember Cli and contains a clean build pipeline, asset management, and unit/functional testing. It's pretty heavily WIP - you probably don't need anything in here if you just stumbled in here.
A preview of the tool is available here, which is automatically built and deployed from master.
You will need the following things properly installed on your computer. If you're developing in Windows, make use of the documentation and the tools we wrote for developing Ember Cli apps on Windows. In particular, you might want to install ember-cli-windows to improve build speed performance. Additional performance can be gained by using an elevated prompt, which can be achieved by starting PowerShell or CMD ‘as Administrator’.
If you have none of the tools outlined below, consider using the amazing Chocolatey to make the installation of those tools a lot easier.
- Nitrogen will attempt to call itself on the same port the host is running on. Unless you're developing with
ember serve --port 80, Nitrogen won't be able to get in touch with the mothership. If the app is started withember serve, live tracking will therefore not work.
git clone https://github.com/felixrieseberg/OxideFleet.gitthis repositorycd OxideFleetnpm installbower install
The included live-development server has automatically reloads on file changes can be started with the following command.
ember serve- Visit the at http://localhost:4200.
Make use of the many generators for code, try ember help generate for more details or visit the ember-cli guide.
ember build(development)ember build --environment production(production)
Integration and unit tests can be run with ember test; use ember test --server if you'd like to test continuously during development. Code style and good JavaScript practices are enforced via JSHint and JSCS, use grunt test to run those tools.