0nft

Run helm charts individually

znft

  • Here 0nft-ui, 0nft-server & postgres pod will get launched.

  • Its counts should not be changed as different pods cannot be attached to different ports. While replicas can be controlled by setting the replicaCount as mentioned in values.yaml.

  • Resources limits and configmap values can also be controlled by setting them in helm command.

  • Docker images for UI & server both refers to same repo in docker hub. So, using common staging tag with prefixes ui- & serv-.

  • Create new subdomain for 0nft with 0nft.<network url>. Example- 0nft.beta.0chain.net.

  • It will generate its own ingress with the name znft-ingress & domain 0nft.beta.0chain.net.

  • Example for its usage in single command, you must use the namespace according to your network name. Also other values can also be set according to requirements:-

    helm upgrade --install --wait -n beta 0nft \
    --set znft.hostName=beta \
    --set znft.host=0chain.net \
    --set znft.image.tag=ui-staging \
    --set znft.serverImage.tag=serv-staging \
    --set znft.config.zcn_config.blockWorker=https://beta.0chain.net/dns \
    0chain-helm/znft

  • Note: By default persistence.enabled: false. It means it will use openebs to create pvc's. In case if it is true, it will create pv as well as pvc's.

  • Note: While specifying the hostName & host in helm command it will create the complete required URL. Example: In beta.0chain.net hostName will be beta & host will be 0chain.net. Necessary Urls will automatically get replaced in various configs/deployment files, if it is specified correctly.

PreviousAuthorizerNext0swap

Last updated