dselman
commented
6 years ago Netlify doesn't support deploying on a tagged release build, so deploy will happen on any changes to master. I have created the branch unstable for changes that we do not want to be automatically deployed.
[x] We host the common models using Netify, registering a domain name link accordprojectmodels.org or some-such
[x] We put in place a Travis build script that deploys the models to Netify using the CLI here: https://www.netlify.com/docs/cli/ On a release (tagged build) we'd deploy to production, otherwise we deploy to unstable.
[x] We add a new URL mapping for Composer, so we can write something like
import org.accordproject.cicero.contract.AccordClause from ap://cicero/contract.cto(https://github.com/hyperledger/composer/blob/master/packages/composer-common/lib/introspect/loaders/githubmodelfileloader.js)I think this gives us the control we need to have a versioned, testable DevOps pipeline for the models In time the generated static site hosted on Netlify for the models can get more elaborate, allowing html/uml generation for the models, search etc. (edited)