this question arose in me when I was trying around with installing a hApp using the Admin Websocket API. First I was using a sandbox holochain service (side question: What is actually sandboxed when running
That way of running a Holochain service is for development and testing. So I moved on to simply running
holochain and then found out about the conductor configuration file. A generated config file will use the user’s home directory for settings and the databases. Therefore I’d consider it the (or a?) global conductor.
Then I saw that
holochain accepts a
-c option so I thought I might as well create a conductor config local to the app that I’m building and point to it. I consider that a local conductor.
All that lead to the question of what are shipped apps using? The global conductor? That would mean that each app needs to start the conductor, figure out the Admin Websocket port and install itself. That would mean significant security vulnerabilities.
So a local conductor. Each app can have its own local conductor, can start it and run it with the databases in a separate folder. No security issue here. But wait, how is one hApp then supposed to interact with other hApps? That can’t be it either.
I found the article on how to ship your hApp and the forum thread on the future of hApp distribution. Holoscape had its last update a year ago - a long time in this dynamic space. The article is missing the images which indicates it’s not up to date either.
If someone would be so kind and point me to the current approach to bundling/shipping an app?