hospital-log/backend/blockchain/network/config/crypto-config.yaml

82 lines
3.7 KiB
YAML

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
# ---------------------------------------------------------------------------
# Org1
# ---------------------------------------------------------------------------
- Name: Hospital
Domain: hospital.com
EnableNodeOUs: true
# ---------------------------------------------------------------------------
# "Specs"
# ---------------------------------------------------------------------------
# Uncomment this section to enable the explicit definition of hosts in your
# configuration. Most users will want to use Template, below
#
# Specs is an array of Spec entries. Each Spec entry consists of two fields:
# - Hostname: (Required) The desired hostname, sans the domain.
# - CommonName: (Optional) Specifies the template or explicit override for
# the CN. By default, this is the template:
#
# "{{.Hostname}}.{{.Domain}}"
#
# which obtains its values from the Spec.Hostname and
# Org.Domain, respectively.
# ---------------------------------------------------------------------------
# - Hostname: foo # implicitly "foo.org1.example.com"
# CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
# - Hostname: bar
# - Hostname: baz
# ---------------------------------------------------------------------------
# "Template"
# ---------------------------------------------------------------------------
# Allows for the definition of 1 or more hosts that are created sequentially
# from a template. By default, this looks like "peer%d" from 0 to Count-1.
# You may override the number of nodes (Count), the starting index (Start)
# or the template used to construct the name (Hostname).
#
# Note: Template and Specs are not mutually exclusive. You may define both
# sections and the aggregate nodes will be created for you. Take care with
# name collisions
# ---------------------------------------------------------------------------
Template:
# Ubah sesuai dengan jumlah node peer yang digunakan.
Count: 3
SANS:
# List dari Subject Alternative Names (SANS) yang akan disertakan dalam sertifikat TLS
# untuk node peer. Ini dapat mencakup alamat IP, nama host, atau
# pengenal lain yang akan digunakan oleh node peer untuk berkomunikasi secara aman
- localhost
- "127.0.0.1"
- peer0.hospital.com
- peer1.hospital.com
- peer2.hospital.com
# Start: 5
# Hostname: {{.Prefix}}{{.Index}} # default
# ---------------------------------------------------------------------------
# "Users"
# ---------------------------------------------------------------------------
# Count: The number of user accounts _in addition_ to Admin
# ---------------------------------------------------------------------------
Users:
Count: 1
# Ubah sesuai dengan jumlah node orderer yang digunakan dalam jaringan.
OrdererOrgs:
- Name: Orderer
Domain: hospital.com
Specs:
- Hostname: orderer
SANS:
# List dari Subject Alternative Names (SANS) yang akan disertakan dalam sertifikat TLS
# untuk node orderer. Ini dapat mencakup alamat IP, nama host, atau
# pengenal lain yang akan digunakan oleh node orderer untuk berkomunikasi secara aman
- "localhost"
- "hospital.com"