TZComet
Contract Metadata Viewer on Tezos
Install / Use
/learn @oxheadalpha/TZCometREADME
TZComet: Tezos Contract Metadata
<div><a href="https://user-images.githubusercontent.com/617111/97904884-235dd900-1d0f-11eb-9aae-28e60eb0af15.gif"><img width="80%" src="https://user-images.githubusercontent.com/617111/97904884-235dd900-1d0f-11eb-9aae-28e60eb0af15.gif" ></a></div>… currently running at https://tzcomet.io …
Part of the development happens in a “monorepo”: oxheadalpha/flextesa-tzcomet-monorepo.
Build
./please.sh ensure setup # Creates an opam switch
./please.sh build all
⬑ if all goes well, last command should print out a link to open the app, like
file://$PWD/_build/default/website/index.html.
Note
The module Tzcomet_jsonm was copied from:
- repository: https://github.com/hhugo/tree/jsoo-friendly
- branch: jsoo-friendly
- commit: a092b96d20302ffa50c1f10c2ac6bf81c7cff9cf
This fork of Jsonm fixes the stack overflow error that can occur when parsing large objects in JSOO.
Deployment
This of course, requires push access to
oxheadalpha/TZComet for it to impact
tzcomet.io (but one can make it happen in their own fork
and it will be at <org-or-user>.github.io/TZComet).
First time, create a local gh-pages branch:
git branch gh-pages -t origin/gh-pages
To deploy the current working directory to /staging:
./please.sh deploy togithub
# Current branch is now gh-pages
git push origin gh-pages
git checkout master # or back to where you were
(this calls does trigger the build).
To deploy origin/master to production:
prod=true ./please.sh deploy togithub
# And push like for /staging
