Running toolbox in browser

[olichwiruk]

Hi!
For our case we had to run this project in browser, and we wonder what was the reason to choose electron?
If you are interested in providing version able to run in browser I can prepare pull request adding ability to run it with vue-cli-service. Just let me know if you find it useful, so we can talk about details.

[dbluhm]

Sorry for such a late response! The main reason we went for electron was because we liked the idea of having a standalone desktop app. Running the toolbox from the browser should in theory be possible but delivering the assets to run it and storing keys in the browser bring up security concerns that should be carefully considered.

[swcurran]

We'd be interested in this for demos and workshops. We saw a demo of this last week on an Aries call and would love to be able to use it that way.

[mitfik]

The keys in web browser can be secure by the provider we could investigate options there. But overall for sandbox environment/demos/workshops this is great option.

Not sure what would be best option but maybe we could have separate branches one for a web version and keep master for standalone version. The code base should be more less the same. We could keep that up to date.

[bartekus]

Would the team be onboard if an alternative would be implemented using full-stack server rendered implementation?
Our team has been utilizing Remix.run internally to essentially simplify/bridge the chasm between server/client code base while ensuring that security is of the primary concern while building our internal test tooling and we are having great results in that use case. The caveat here however is that our implementation leverages reactjs as the ui library as well as adds supabase (the use of supabase gives us authentication/authorization, storage, real time functionality all while ensuring high level of security) to the mix to leverage as much as possible open source provided and tested functionality without reinventing the wheel.