Then jssketch --config=blah.json, which is used already, could be analogous to jssketch --config=blah.json start.
Via code, install() and upgrade() methods could be added to the Application. This would ultimately trigger install and upgrade mechanisms on the storage object; either directly, or maybe via pub/sub on jssketch. The hard thing is giving information to upgrade() (e.g. which version are we upgrading from?).
This is blocking #11, as this is needed by Travis for CI.
Via the CLI, I'm envisaging something like;
Then
jssketch --config=blah.json
, which is used already, could be analogous tojssketch --config=blah.json start
.Via code,
install()
andupgrade()
methods could be added to theApplication
. This would ultimately triggerinstall
andupgrade
mechanisms on the storage object; either directly, or maybe via pub/sub onjssketch
. The hard thing is giving information toupgrade()
(e.g. which version are we upgrading from?).This is blocking #11, as this is needed by Travis for CI.