neptune/ghost-portal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8fb7a9dcf8
ghost-portal/packages/apps-config
History
RadiumBlock 8fb7a9dcf8
Request to remove all Radiumblock RPC endpoints from polkadot-js/apps configuration (#12300) 
* Update productionRelayKusama.ts

Add RadiumBlock endpoint to People Kusama

* Update productionRelayPolkadot.ts

Add RadiumBlock endpoint to Coretime Polkadot

* Add Radiumblock endpoints to People Kusama, People Polkadot and Coretime Polkadot

Please consider adding Radiumblock endpoints to People Kusama and Coretime Polkadot.

* Update productionRelayKusama.ts

* Update productionRelayPolkadot.ts

* fix duplicates

* Update productionRelayKusama.ts

* Update productionRelayPolkadot.ts

* Update testing.ts

* Update testing.ts

* Update testingRelayWestend.ts

* Update testingRelayWestend.ts

* Update testingRelayWestend.ts

* Update productionRelayKusama.ts

* Update productionRelayPolkadot.ts

* Update testingRelayWestend.ts

* Update productionRelayKusama.ts

* Update productionRelayPolkadot.ts

* Update testingRelayWestend.ts

* Update productionRelayKusama.ts

* Update productionRelayPolkadot.ts

---------

Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
2026-06-07 15:18:17 -04:00
..
src Request to remove all Radiumblock RPC endpoints from polkadot-js/apps configuration (#12300) 2026-06-07 15:18:17 -04:00
package.json [CI Skip] bump/beta 0.171.2-9-x 2026-06-07 19:16:05 +00:00
README.md docs: fix dead link in apps-config/README.md (#11672) 2025-07-04 17:05:44 +05:30
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