A local browser using manifests as the data source.
TARO ships with several default apps/channels, and the user can add more by supplying a URL to a web page (or a manifest).
Upon submitting a URL, TARO will follow the URL to the linked manifest (the W3C standard kind), storing the contents in the user's local TARO database (all on the client). Using several of the standard manifest keys, plus some custom ones, we have all the data we need to render the metadata and stylise the app in the TARO dashboard.
Think Roku (or Firefox OS) but totally accessible as a web page (or embedded as a web page from a desktop executable app, à la the browser.html project).
You can watch a short screencast of where I'm at right now.
You can also play with a live demo of TARO:
http://taro-vr.herokuapp.com/
To install from npm:
npm install taro
To install the Node dependencies from a cloned copy of the git repository:
npm install
Generate a local settings file:
cp settings_local.js{.dist,}
To run the file watchers, run this from one terminal session:
npm run watch:js
And run this from another terminal session:
npm run watch:css
And from yet another terminal session, serve the site from the simple server:
npm run dev
Then launch the site from your favourite browser:
If you wish to serve the site from a different port:
TARO_PORT=8000 npm run dev
- JS is edited in
src/. jsxcompiles those files and puts them inlib/. These built files are used by the server.- Files in
lib/are built for the client usingbrowserifyand put instatic/.
static/ and lib/ are not checked in. So be sure to run npm run build before running the server. (npm start takes care of this in production, and npm run dev/npm run watch:js take care of this in development.)
In production, the server is run like so:
npm start
Alternatively:
npm run prod
To run the server à la Heroku:
foreman start web