neptune/ghost-portal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4659cb968b
ghost-portal/packages/apps-config
History
SURF 4659cb968b
Onfinality remove Kilt (#10885) 
* add onfinality endpoint for polkadot and kusama

* Add OnFinality Westmint endpoint

* added OnFinality API for BridgeHub Kusama

* added OnFinality API for BridgeHub Westend

* added OnFinality BridgeHub Polkadot API

* Added multiple OnFinality API

* Added OnFinality Equilibrium API

* added OnFinality API for Bitgreen

* added OnFinality API for Darwinia

* added OnFinality API of Polkadex Parachain

* added OnFinality API Darwinia back

* added equilibrium OnFinality API back

* add polkadex-parachain and get polkadot-js new version

* Add Moonbeam , Moonriver, Moonbase Alpha back to Polkadot.js

* Add to Kusama krest Polkadot.js

* add peaq network

* remove Peaq network

* edit peaq

* added Onfinality CommuneAI endpoint

* reorder key

* 删除network

---------

Co-authored-by: ian.he <ian@onfinality.io>
Co-authored-by: Mike Xing <mike.xing@onfinality.io>
Co-authored-by: Xing <mikespook@gmail.com>
Co-authored-by: jiajing.chen <jiajing.chen@onfinality.io>
Co-authored-by: Xing <675230+mikespook@users.noreply.github.com>
2024-09-05 10:52:40 -04:00
..
src Onfinality remove Kilt (#10885) 2024-09-05 10:52:40 -04:00
package.json [CI Skip] bump/beta 0.143.3-13-x 2024-09-05 12:21:41 +00:00
README.md add Hyperbridge networks (#10328) 2024-03-04 08:46:44 -05:00
tsconfig.build.json Switch on tsconfig composite (#9465) 2023-05-19 15:11:59 +03:00
tsconfig.spec.json Switch on tsconfig composite (#9465) 2023-05-19 15:11:59 +03:00

README.md

@polkadot/apps-config

General config for various services, including settings, external links & types. This is a central source of all the configuration settings that can be tweaked. This also means that it can be customized (via PR) to support any additional chains. The internals are split into a number of settings -

  • api - Here you can add any chain or node-type specific types configuration. When added, it means that when the UI connects to either a runtime with a spec name, or a chain with a specific name, the types will be automatically added to the API as used in the app.
  • endpoints - Configuration for specific per-type chain endpoints.

Customization for each of these are discussed next.

Api

The API config can be done in one of two ways -

  • chain - Here we are mapping to a specific chain name. Generally the next type would be preferred, however if you are supporting multiple chains with individual configs, you would probably want to add the chain-specific information in here.
  • spec - Here we are mapping from the runtime spec name of the chain to specific types. This means that when connected to a specific spec, these types will be injected.

The actual type definitions you should be familiar with, it is exactly the same as you would upload via the settings page in JSON, or as detailed in the API types pages.

Endpoints

  1. Add your chain logo (if available) to either ui/logos/chains or ui/logos/nodes (the second is generally used)
  2. Run the image build command to generate an inline version via yarn build:images
  3. Add your chain to endpoints/{production, productionRelay, testing, testingRelay*} as applicable for your deployment
  4. The ui.color specifies the chain color, the ui.logo (imported from generated), specifies the specific logo