Fork 0

mirror of https://github.com/pezkuwichain/pezkuwi-apps.git synced 2026-10-20 18:56:30 +00:00

Files

T

Satoshi Qazi Muhammed 66e8d6c1be apps-config: drop the foreign chains' logos, links and identity icons

- 87 chain and all 185 node logos were referenced by nothing once the
  foreign endpoints went; the images are removed and imgConvert no longer
  generates a nodes set. Pezkuwi and Zagros logos remain.
- External links: none of the 14 services serves a Pezkuwi chain. Most
  are third-party sites whose chain keys had been renamed by the rebrand
  (on Zagros they linked to commonwealth, subsquare and others for
  another chain's data); stats., statescan. and scan.pezkuwichain.io do
  not resolve, explorer.pezkuwichain.io is a placeholder and treasury./
  governance. redirect back to this app. externalLinks is empty until a
  service indexes a Pezkuwi chain; their logos are removed too.
- Identity icons: the centrifuge, joystream, litentry, dicle and paseo
  entries are removed.

2026-10-10 04:54:16 +04:00

src

apps-config: drop the foreign chains' logos, links and identity icons

2026-10-10 04:54:16 +04:00

package.json

apps-config: drop the foreign chains' type bundles

2026-10-10 04:54:16 +04:00

README.md

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

tsconfig.build.json

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

tsconfig.spec.json

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

README.md

@pezkuwi/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

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