I would like to have a single instance of Daml-UI-template which can connect to multiple DAML JSON API instances (e.g. Alice -> localhost:7500, Bob -> localhost:7501) based on the party. In the Layout file, where the DamlLedger react component is instantiated, I can choose the right JSON API host/p…

In production, you’d end up running each of the JSON APIs behind a reverse proxy to terminate SSL and deal with CORS so your questions is only relevant to development I think. And for development, you can get rid of CORS using CORS Anywyere . It’s a dynamic reverse proxy that just allows you to make …

Daml-ui-template: use a different JSON API instance for each party

Questions

anthony Split this topic June 2, 2020, 8:19pm 5

A post was split to a new topic: Why run a separate json-api for each party?

Topic		Replies	Views
Daml-ui-template Questions ledger-api	31	1479	May 7, 2021
Does the React UI template already support the the Party management API functions like `listKnownParties`? Questions	2	301	March 23, 2021
Query party IDs for login screen Questions daml , react , template , json-api	1	545	June 3, 2020
Cors issue with Daml Hub Questions daml , damlhub , json-api	8	687	September 30, 2022
HTTP JSON API and navigator connected to same ledger but getting different parties Questions navigator , json-api	3	232	March 7, 2022

Daml-ui-template: use a different JSON API instance for each party

Related Topics