In 7b3e07d we were forced to integrate use of the admin websocket into our connector logic to work around https://github.com/holochain/holochain/issues/1746. This is not a long-term solution as "normal" Holochain apps will probably not have access to this websocket in future. (Because of this, I'm considering this a bug.)
The new hc launch utility looks like it could be a better bet for use in development, and has a pretty simple CLI interface.
However, our development pipeline may need to be updated to perform full build steps and bundling in order to run through this utility- it's unclear whether a separate development server (with hot reload capabilities) can be made compatible.
I suspect we want the best of both worlds here (near-instant development feedback and simple bootstrapping). Will need to investigate further to see if this new utility affords that possibility, or if we will need to resolve the upstream Holochain issue differently.
In 7b3e07d we were forced to integrate use of the admin websocket into our connector logic to work around https://github.com/holochain/holochain/issues/1746. This is not a long-term solution as "normal" Holochain apps will probably not have access to this websocket in future. (Because of this, I'm considering this a bug.)
The new
hc launch
utility looks like it could be a better bet for use in development, and has a pretty simple CLI interface.However, our development pipeline may need to be updated to perform full build steps and bundling in order to run through this utility- it's unclear whether a separate development server (with hot reload capabilities) can be made compatible.
I suspect we want the best of both worlds here (near-instant development feedback and simple bootstrapping). Will need to investigate further to see if this new utility affords that possibility, or if we will need to resolve the upstream Holochain issue differently.