commit | d83ac7ed9534e43b99b3930fef52238816842494 | [log] [tgz] |
---|---|---|
author | Nicolas Lacasse <nlacasse@google.com> | Mon Oct 19 15:46:23 2015 -0700 |
committer | Nicolas Lacasse <nlacasse@google.com> | Mon Oct 19 15:46:23 2015 -0700 |
tree | 5dd1a1737523521d2ca6aad12a5a5f2481f86c30 | |
parent | 89cfb875d552fda0889e5d9253618bb7be88324a [diff] |
"npm link" vanadium instead of "npm install" "npm install" puts a full copy of vanadium inside the travel repo, including the .jiri metadata file. This confuses jiri tool because it finds two projects with the same name at different paths in the project tree. "npm link" creates symlinks, which jiri will not follow, thus avoiding this issue. All of our projects currently use "npm link", except for travel. At some point we will want to do something better than "npm link", but this is good enough for now. Change-Id: Iad79f57a81b64908176e94d6487877b8cfbb5bc0
An example travel planner using Vanadium.
If you have a $JIRI_ROOT
setup you can install Node.js from $JIRI_ROOT/third_party
by running:
jiri profile install nodejs
Optionally, it is possible to use your own install of Node.js if you would like to use a more recent version.
The default make task will install any modules listed in the package.json
and build a browser bundle from src/index.js
via browserify.
make
It is possible to have the build happen automatically any time a JavaScript file changes using the watch tool:
watch make
Local instances require a blessed syncbase instance. To attain blessings and start syncbase, use:
make syncbase [creds=<creds subdir>] [port=<syncbase port>]
Related target:
make creds [creds=<creds subdir>]
You can similarly run with fresh creds or syncbase data via:
make clean-creds make clean-syncbase
To run a local dev server use:
make start [port=<port>]
To connect to a syncbase instance other than the default, navigate to:
localhost:<server port>/?syncbase=<syncbase name or port>