►
Description
A virtual meetup hosted by Hyperledger Seattle on October 27, 2021 featuring Varad Ramamoorthy and David Huffman sharing about the Fabric Operations Console. Learn about how Fabric Operations Console can be used to manage your Fabric network. This session would start with a quick demo followed by AMA. Ask the Fabric Operations Console maintainers about anything ranging from high level features of console to specific challenges you are running into with getting console running.
The Fabric Operations Console repo is at: https://github.com/hyperledger-labs/fabric-operations-console
A past session on Fabric Operations Console is at https://www.youtube.com/watch?v=ndrWBoBlTDM
More about this event is at: https://www.meetup.com/Hyperledger-Seattle-Chapter/events/281416743/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerMeetup #Blockchain
B
A
Yeah
so
looks
like
we
happy
enough
people
and
let's
get
started,
thank
thank
you,
verad
and
david
being
with
us
again
from
ibm.
So
maybe
you
can
intro
yourself
a
little
bit
and
have
a
briefing
of
the
last
session.
This
is
a
follow-up
ama
for
from
the
last,
a
good.
The
presentation
that
there's
a
lot
of
questions
and
the
thoughts
then
feel
free
to
discuss
in
this
session.
So
over
to
you
all
right.
B
Okay,
all
right
thanks
david
and
yeah,
so
for
organizing
and
arranging
the
session.
So
this
is
the
ama
session
for
the
console
right.
You
know
so
the
fabric
operations
console.
So
so
let
me
give
people
an
introduction
right.
You
know
I
mean
we
covered
fairly,
not
too
deeply,
but
the
reasonable
level
last
time
right
in
terms
of
how
to
set
up-
and
you
know
how
to
run
it
and
everything.
So
I
will
probably
take
about
10-15
minutes
of
the
first.
B
You
know
session
talking
about
again
the
console
and
the
intro
some
of
the
things
we
covered
last
time.
So
people
have
a
context
right
and
then
we
will
dive
into
any
questions.
You
guys
might
have
right.
So
then
we'll
cover
it
and
I
am
brad
ramon,
one
of
the
lead
architects
for
the
console.
I
work
for
ibm
and
david.
If
you
want
to
introduce.
C
B
Right
thanks
david
yeah,
anything
api.
You
know
that
you
see
in
the
code,
it's
all
it
all
came
from
david,
so
so
on
the
console
again
quickly
right.
You
know
so.
People
currently,
of
course,
use
hyperledger
fabric.
You
know
for
setting
up,
you
know
again
their
orders
peers
and
you
know
cas
and
such
right
and
what
you
know
the
console
helps
with
and
does
is
managing
the
fabric
side
of
things
right
in
a
easy
to
use
interface
right.
B
So
you
can
do
a
you
know
again,
I'm
not
going
to
go
through
each
of
these
bullets,
but
you
can
again
manage
your
fabric,
like
you
know,
create
channels,
and
you
know,
install
chain
code
and
you
know,
use
the
two
old
life
cycle
and
you
know
update
the
channel
in
a
lot
of
those
fabric.
Things-
and
you
know
what
you
know.
I'm
sure
people
ask
like.
Can
I
create
components
right?
That's!
No!
B
You
cannot
right
and
that's
one
of
the
things
that
we
will
be
having
an
interface
for
at
some
point
right
at
the
moment.
You
know
the
you
know.
That
is
that's
not
something
you
can
do
with
the
open
source,
but
there
are
other
ways
to
do
it
right.
So
so
what
again
high
level
architecture
diagram
right
you
got,
the
browser
and
console
is
what
we
are
talking
about
in
this
context:
right
and
console
talks
to
your
peers
and
orders
using
a
grpc
proxy.
B
B
You
know,
or
you
know,
protocol
right,
you
know,
but
then
we
will
talk
back
in
grpc
like
you
know,
back
to
the
orders
and
tears
right
like
this
picture,
and
we
again
will
also
proxy
the
calls
via
config
translator.
Again,
the
reason
being
you
need
to
have
all
of
it
in
the
same
domain,
and
you
know
if
you're
doing
local
development-
and
you
know
simpler
setup-
you
don't
need
to
like
you
know,
have
nginx
or
some
something
running
good,
but
instead
you
know
you
can
proxy
the
call
over
on.
B
You
know
to
config
translator,
and
you
know
this-
the
backing
databases
couch
in
this
case
right.
So
that's
kind
of
a
quick
architecture
right
diagram
and
in
terms
of
running
the
console,
it's
fairly
straightforward
right.
You
know
that
is
basically
cloning
three-step
process
really,
so
the
first
part
is
setting
up
the
network
itself
right.
That's
in
this
case.
You
know
we
use
the
test
network
from
fabric
right.
So
if
you
look
at
the
scripts,
you
know
the
setups,
for
you
know,
network
script.
B
You
will
see
in
all
the
commands
it
uses
like
you,
know,
cloning
it
and
changing
it
to
like
two
to
three
and
you
know
provisioning
it
right.
It's
been
fairly
consistent
right,
so
you
can
set
up
a
network
and
then
the
second
part
is,
you
know,
setting
up
the
console.
Basically,
the
stuff
we
just
saw
right
like
which
is
console.
It
will
create
couchdb,
it
will
create
grpc
proxies
and
it
will
create
config
translator,
all
in
docker,
compose
right
and
then
that's
basically,
the
second
part
of
it.
B
What
the
third
part
is
is
basically
the
create
asset
right.
What
the
create
asset
will
do
is
it'll,
take
the
existing
running
test
network
and
then
create
a
you
know,
json
files
that
the
console
is
able
to
take,
and
so
you
can
just
simply
import
them
so
that
the
console
is
tied
to.
I
guess
you
know
the
fabric
components
right,
that's
kind
of
the
three-step
process,
and
once
you
do
that
again,
you
know
you
can
go
through
the
steps
to
basically
create
certificates.
B
You
know
we
can
briefly
see
some
of
that,
but
what
I
did
in
advance
is,
I
you
know,
ran
the
setup
network
script.
As
you
can
see,
you
know
to
save
some
time
right.
So
this
is
all
again.
You
know
going
to
fabric
samples
and
then
creating
a
network.
Nothing
specific,
that's
console
in
this
case,
and
then
the
next
step
we
would
do
is
you
know,
console
up
what
this
will
do?
Is
it
will
die
it'll
again
go
here.
B
The
docker
composer
will
download
the
you
know
it
already
downloaded
before
right,
the
the
console
image
and
then
start
that
up
then
the
last
step.
The
third
step
right
is
creating
the
asset.
Again.
This
will
connect
to
the
existing
network
right
the
test
network
and
then
massage
the
files
and
create
these.
You
know
json
files
and
then
put
them
in
a
zip
file,
so
you
can
simply
import
them
into
the
console
right
at
this
point.
That's
all
it
took
right
so
other
than
creating
the
network.
B
It
should
literally
take
like
you
know,
depending
on
the.
If
the
image
is
downloaded
or
not
in
a
couple
of
seconds,
literally
right
once
the
the
the
assets
are
created,
you
should
be
able
to
simply
import,
so
not
that
one
so
this
so
you
would
go
to
localhost
3000,
that's
where
it
will
be
running
and
the
default
is
admin
and
password
right
and
immediately
upon
login.
You
are
required
to
change
the
password
just
a
pointer,
like
you
know,
some
people
indicated
like
at
least
for
local
development.
B
B
B
So
as
long
as
you
have
configured
grpc
you
have
in
front
of
your
orders
appears
you
should
be
able
to
talk
to
it
right,
so
I'm
going
to
import
it
or
if
I'm
going
to
spend
like
maybe
four
minutes
and
then
switch
over
so
within
the
console
that
has
work
area
right
and
then,
if
you
go
in
there,
that
is
the
create
console
assets.
That's
the
new,
zip
file
that
we
just
created.
Then
you
import
it
right,
so
that
should
import
the
components.
So
if
you
go
to
the
nodes,
you
should
see
the
the.
B
B
B
B
You
and
when
you
associate,
we
already
know
based
on
the
root
cert,
that
this
year
has
what
are
the
a
lot
of
certificates
in
your
wallet
that
you
can
use
so
notice
that
you
didn't
see
our
orders
identity?
That's
it
right!
So
now
we
are
able
to
connect
and
talk
to
the
test
network.
Here
now
we
are
able
to
see
that
it
has
my
channel,
which
was
already
created,
and
you
see
that
using
the
tool
you
know
format.
B
B
So
now
you
can.
So
this
is
a
view
of
your
system
channel
right
where
we
see
that
the
order
has
one
admin
or,
and
then
you
have
consortium
members
like
r1
and
r2,
and
you
see
that
in
the
consenters
that
you
know
we
have
one
just
one
node.
If
you
have
multiple
nodes
in
the
cluster,
you
will
see
all
of
them
listed
here
again.
Just
one
node
so
again
the
the
one
last
thing
before
I
will
stop
for
questions
is
you
can
go
into
the
channel
right
and.
B
And
again
I
won't
go
through
the
flow,
but
you
can
easily
follow
the
you
know.
The
install
approve
commit
process
that
fabric
to
olive
cycle
gives
you
right,
so
you
are
able
to
do
that
right
from
directly
from
the
console.
Without
you
know,
going
through
command
line
and
knowing
what
the
you
know,
the
the
payload
is
for
the
commit
process
and
all
that
stuff
right.
So
it
makes
it
super
easy
to.
B
A
B
I
can
you
know
in
this
console,
even
though
I'm
running
locally,
I
can
have
you
know,
node
running
somewhere
else
like
in
ibm,
cloud.
or
whatever,
and
then
simply
import
it
right.
You
know
the
it's
a
json
driven
thing
right,
so
the
network
term
is
kind
of
in
some
ways.
In
my
view,
overloaded
right
so
network
is
just
a
logical
definition.
B
There
is
no
real
network
right,
I
mean
you
can
have
one
clear
talking
to
two
different
ordering
services
right
and
you
can
have
channels
from
you
know
on
the
same
peer
from
two
different
ordering
systems.
So
I
guess
if
the
network
is
kind
of
loose,
but
the
point
is,
if
you
have
peers
order
cas
whatever
the
you
know,
those
fabric
components,
it
can
be
running
anywhere
as
long
as
you
put
grpc
the
front
and
expose
it,
you
shouldn't
be
able
to
import
it
into
console
and
manage
them
without
too
much
trouble
right.
B
Not
necessarily
it
depends
on
like,
so
if
so,
you
need
a
lowest
common
denominator
right,
so
you
can
on
the
same
console
at
one
four
and
two
oh
peers
and
orders,
so
it's
all
channel
driven
at
the
end
of
the
day
right.
You
know
what
does
the
channel
do
so
you
can
have
two
channels
with
one
fourth
capability
and
two
capability,
so
you
can
man.
If
the
question
is,
can
I
manage
different
nodes
with
different
levels
on
the
same
console?
B
Yes,
you
can
so
you
we
support
one
four
life
cycle
and
the
two
whole
life
cycle,
both
of
them,
so
you
can
so
like
right
now
I
have
a
channel
with
two
capabilities,
so
you
see
stuff
that's
relevant
for
duo,
but
if
you
have
a
channel
with
1
4
capability,
you
will
see
a
slightly
different
console.
That
shows
again,
you
know
the
the
one
full
view
of
it.
I
guess.
B
Okay
and
then
participating
is
not
savvy
enough
to
deploy
their
own
node
on
a
providence
project.
Is
there
an
option?
Lightweight
should
be
yeah,
so
you
can
manage
it
right
if
the.
If
the
client
is
not
savvy
enough,
you
can
still
they
can.
I
mean
if
they're
able
to
use
the
ui,
you
can
host
the
ui
anywhere
and
you
can
have
the
components
wherever
and
they
don't
have
to
be
in
the
same
network
right
so
and
then
what
parts
of
console
is
ibm
making
open
source
right?
B
So
what
ibm
is
making
open
source
is
all
of
the
things
you
just
saw
right.
What
we
did
not
open
source
is
the
operator
component
that
allows
you
to
provision,
so
the
internal
ibm,
not
internal.
I
should
say
so.
The
ibm
version
of
open
source
offering
support
offering
that's
the
offering
ibm
has
that
allows
you
to
create
fears
and
orders
and
cas
and
manage
their
resources,
and
you
can
change
like
the
peer
resource
and
ordering
resource
and
all
that
stuff
right.
So
that's
the
kubernetes
aspect
right
that
part
is
isn't
open
source.
B
The
console
is
that's
a
good
question
and
then
so,
okay
and
then
you're
from
google.
How
does
console
wallet
work?
Is
it
in
a
couchdb
wallet
now
so
one
of
the
requirements
we
had
way
back
when
we
started
the
console
development
right
is
to
not
manage
the
keys
and
certificates
for
a
customer
right.
That
puts
us
that
I
don't
know
some.
Some
customers
did
not
like
it.
Some
customers
are
okay
with
it,
but
so
what
we
said
was
you
know
we
won't
store
and
manage
the
certificates
in
any
database
right.
B
So
when
you
import
or
create
the
wallet,
it's
only
in
the
browser's
local
storage
right,
so
it's
not
in
couchdb.
So
one
thing
we
were
considering
you
know
is
to
integrate
with
some
of
the
cloud-based
solutions.
Right
so,
like
you
know,
for
example,
ibm
has
certificate
manager,
and
you
know
amazon
has
its
own
right.
So
integrating
with
some
of
those
solutions.
So
again
the
certificates
are
maintained
elsewhere.
B
But
when
you
log
in
you
pull
the
certificate
from
wherever
the
provider
and
use
it,
but
that's
not
something
you
do
today,
but
you
know
it's
it's
the
the
answer.
Is
we
currently
only
store
it
in
the
local
storage
wallet
right,
we're
interacting
with
the
network
with
the
newly
created
identity?
How
can
we
instantiate
chain
code
if
you
need
to
use
certificate
exists
on
the
channel
config
right?
So
so
you
do,
of
course
yes
need
the.
B
So
if
you
have
one
four
right
and
if
you
have
no
w
things,
are
simplified
a
lot
right.
So
that's
one
of
the
critical
things
right.
So
if
you
have
no
do
you've
enabled
as
long
as
you
get
a
certificate
like
what
we
just
did
right.
So
that
applies
to
one
for
also,
so
you
know
which
is,
I
did
not
import
a
specific
certificate.
I
created
it.
You
know
one
using
admin
type
right
and
I
was
able
to
like
again
interact
with
the
pearson
order.
B
So
so
you
don't
need
the
specific
admin
search.
You
know
if
you
have
node
enabled.
If
not,
then
you
need
to
make
sure
the
wallet
right
contains.
You
know
it's
a
json
format
right,
so
the
wallet
has
the
private
public
key
pairs
to
work
with
the
pier
so
nazari.
Did
I
explain
your
question?
Did
I
answer
your
question?.
A
B
A
B
One
of
the
things
that
wasn't
open
source-
it's
part
of
the
operator,
so
anything
that
you
need
to
have
kubernetes
or
some
kind
of
infrastructure
to
like
manage
the
certificates.
You
know
so
there
is
no
cli
or
there
is
no
command
or
approach.
That
fabric
gives
you
for
certificate
review
right.
You
need
to
actually
renew
the
certificate
and
have
it
on
the
disk
right.
B
So
there
is
no
api
for
certificate
renewal
from
fabric,
which
is
why
the
console
cannot
do
it
and
that's
where
you,
you
need
the
operator
right
to
do
some
of
those
business.
So
now
so
the
so
we
purely
you
know
abstract
the
the
maintenance
of
fabric
from
again
channel
chain
code.
You
know
and
then,
like
you
know,
if
you
are
talking
about
ca,
you
know
you
can
get.
B
That
fabric
does
not
have
an
api
for
that's
done
by
our
operator
and
that's
not
part
of
the
open
source,
so
does
console
supported
system
great
question,
so
the
images
again
this
goes
to
ibms
ibm
with
our
support
offering
we
build
certified
images.
Certified
images
that
support
hsn,
so
so
those
images
supported,
console
doesn't
quite
care
about
hism,
even
though
you
know
it
does
allow
you
to
work
with
hsn.
B
But
again,
obviously
you
know
that
hsn,
you
are
not
going
to
have
the
certificates
locally
write,
the
private
keys
so
for
the
console
to
talk
to
hit
system
enabled
peers,
you
still
need
a
certificate
on
local,
so
we,
the
console,
doesn't
do
direct
hsn.
If
that
that
makes
sense,
so
you
still
need
certificates.
Console
is
doesn't
have
like
a
you
know
the
clients
to
talk
to
hsn.
B
It's
all
happening
on
the
browser
right.
How
can
I
manage
external
intermediate
ca?
So
so
you
could
have
you
know
again.
You
could
have
two
different
cas
right,
external.
You
know
intermediate
cas
in
the
console
two
different
ones
right
and
again
the
support
offering
that
we
have
allows
you
to
provision
and
manage
the
fabrics
ca.
You
know
the
server
yaml
and
all
that
stuff
right.
So
that's
all
possible,
so
console
does
like
within
the
msp
definition
when
you
create
one.
So
you
could.
B
So
what
it
will
show
is
you
pick
a
ca.
You
can
see
that
right.
So
we
populate
with
what
the
root
cert
is
for
that
ca,
but
you
do
have
the
flexibility
to
add
your
other
route
search
and
tls
search.
So
if
you
have
intermediate
cas
right
your
you
know,
you
can
include
their
certificates
also
right
and
if
you
export
it,
even
you
get
even
more
flexibility
right.
You
can.
B
Freeform,
like
you
know,
include
the
you
know
like
multiple
certificates
and
just
make
up
your
own
msp
definition
right
so
yeah.
So
I
think
you
know
the
the
console
does
allow
you
to
use
the
intermediate
cas.
If
that's
what
you
have
okay,
so
the
next
question
regarding
nordo:
u
it
only
works
with
some
operations
like
install,
but
instance
it
works
on
channel,
so
the
channels
also
have
modal
use.
So
if
you
go
into
the
console,
let
me
show
you.
B
So
if
you
go
into
the
channel
specifically
right
and
then
go
to
the
channel
details,
you
can
see
that
in
this
case
I
have
org
one
and
two
and
both
have
no
w.
So
the
node
o.
U
is
applicable
for
the
install
side
where
the
pier
itself
has
config
yaml.
That
dictates
your
node,
u
configuration
and
then
the
channel
also
within
the
msp
definition.
C
B
Is
a
cool
capability
you
have
in
console
so
once
you
have
console,
let's
say
you
drill
down
into
a
channel
right,
so
you
can
add
debug.
You
can
spell
it
right,
so
debug
in
front
of
the
url
and
what
you
will
see
is
right.
There
is
a
new
option
that
will
show
up
called
open
channel
config.
This
is
incredibly
useful
because
again
you
don't
have
to
go
to
cli
to
download
and
decode
and
all
that
business.
So
what
I
was
going
to
show
you
was
right,
so
r1
msp.
B
So
if
you
look
at
the
r1
msp
definition
and
then,
if
you
keep
drilling
down,
you
see
this
section
right
within
the
msp,
so
you
see
the
organizations
right
there
right
so
part
of
the
channel.
Config
is
also
nodo.
U,
and
you
know
again,
you
know
it's
it's
configured
with
enable
true
in
this
case,
which
is
why
the
console
shows
that
information
and
since
we
are
on
this
page
right,
so
you
can
inspect
like
the
policies
and
it's
basically
the
entire
channel
things
we've
done.
B
You
know,
like
you,
see
that
the
anchor
pier
is
such
right.
You
know
for
that
organization.
So
you
see
all
of
these
information
again,
you
know
it's
super
helpful
for
debugging
purposes,
and
so
yes,
the
node
of
view
is
applicable
for
both
the
admin
of
the
peer
and
also
on
the
channel
decentralized
august,
great
question
right.
So
so
you
could
have
distributed
orders
and
fears.
So
within
the
console
you
you
can
like,
let
me
go
down
into
the
artwork.
B
B
B
B
You
know
added
organization
that
want
to
contribute
some
of
the
orders,
so
you
can
simply
add
them.
Right,
add
them
to
the
order.
Admin
and
the
moment
you
add
it
to
the
list
of
ordering
service
administrators
right.
They
can
now
add
their
own.
You
know
again
their
own
orders
to
the
cluster
and
you
you
can
now
have
orders
from
different
organizations
different
cloud
providers
if
you
want
it
to
be
and
then
manage
them
directly
from
the
console.
B
B
B
So
right,
oh
okay!
So
since
I
don't
have
multiple
orders,
so
the
ordering
services
right.
So
if
you
we
do,
allow
you
to
update
the
consent
or
set
on
the
channel.
That's
the
that's
the
important
bit
right.
So
since
I
have
only
one
node
in
the
whole
thing
right,
you
know
I
don't
have
the
ability
to
do
that.
But
if
you
have
multiple
consenters
right
you
know,
then
you
can
pick
and
choose
which
of
the
ordering
nodes.
B
You
want
to
be
a
consenter
on
the
channel
and
then
you
can
join
the
channel
to
the
relevant
peers
you
want
to
like
you
know,
only
certain
peers
are
on
certain
channels
right.
But
the
point
is,
I
guess,
the
the
the
orders
are
distribu.
You
know
you
can
associate
different
consenters
in
different
channels
and
that's
something
the
console
allows
you
to
do.
B
B
So
so
any
other
questions,
people
have
right,
really
good
questions.
I
love
the
session
okay,
so
so
you
know.
So
if
there
are
some,
you
know
david.
You
know,
I
guess
huffman
writing.
If
you
want
to
show
so
one
of
the
things
I
know
people
have
asked
in
the
past
that
I'm
bringing
up.
How
do
I
set
up
the
console
to
do
tls
right
because
obviously
the
default
is
non-tls
and
one
pointer
I
would
like
to
make
is
right
if
you
access
console
in
non-tls
fashion,
anything,
that's
not
localhost.
B
Like
I
don't
know,
you
know,
broad.ibm.com
or
whatever
right
in
non-tls.
It
won't
work
properly
because
you
know
the
there
is
a
security
package
that
david
can
talk
about
right.
You
know
we
use
that
require
that
will
only
work
when
you
are
in
you
know,
tls
mode.
Unless
again
you
are
in
localhost
mode
right.
So
let
me
stop
sharing
for
a
bit
and
then
let
david
show
you
guys
how
to
configure
console
for
tls
right.
C
C
So
if
you
already
have
a
proper
cert
put
the
search
somewhere
in
the
file
system,
that's
in
the
repo-
and
then
point
point
these
at
that.
So
this
is
your
private
key.
This
is
your
certificate
file
and
then,
if
you
don't
have
a
cert
and
you
just
want
to
make
a
self-signed
one
just
to
get
through
it,
you
can
just
point
this
to
a
blank
or
a
non-existent
file
and
then,
when
it
starts,
it
will
create
a
self-signed
certificate.
So
I'll
show
that
actually
so
there's
my
copy
paste.
C
So
on
the
right
here,
I'm
just
showing
you
pretend
these
are
your
environmental
variables
that
you
would
set
up.
I
have
a
script
that
will
just
load
these
into
my
environment,
so
you
would
set
these.
However,
you
want
for
whatever
os
you're
running
and
I'm
pointing
at
this
particular
folder,
and
if
we
look
at
that,
folder.
C
C
Silly
log
that
will
print
out
here
silly
level,
so
this
level,
so
it
started
the
app
on
port
3000
and
there's
an
s
at
the
end
of
that.
So
we
know
it
did
tls
and
we
look
up
a
little
bit.
There's
some
logs
about
it,
saying
that
the
tls
cert
wasn't
found.
So
it's
going
to
generate
it,
and
if
I
open
that
directory
we
can
see
new
files.
So
that's
good.
C
C
So
that
looks
good,
so
I'll
just
accept
that
and
then
it'll
prompt
me
to
enter
the
console
and
now
it's
just
kind
of
business.
As
usual,
I
can
log
in
a
user
I've
created
and
I'm
in
my
console,
so
that's
tls
and
again,
if
you
have
a
proper
cert
one
that's
signed
by
you
know
a
third
party.
You
would
just
point
this
path
to
somewhere
in
the
file
system
to
that
cert
all
right,
stop
on
the
server
any
questions
on
that.
C
B
C
So
tls
done:
what
else
should
we
do?
So
we
can
talk
about
some
of
the
settings
that
people
might
want
to
change.
So
a
lot
of
the
default
settings
are,
you
know,
pretty
good
defaults,
but
they
might
not
fit
for
some
circumstances,
so
the
default
file
is
here
and
some
packages,
the
athena
json
docs
default,
setting
dots.
This
is
where
you
can
see
all
the
default
values,
but
I
don't
recommend
changing
it
here.
B
C
C
So
in
my
case,
I
have
a
config
file
that
I'm
using
config
dsh,
and
these
are
some
of
the
overrides
I've
already
set
and
let's
go
through
some
of
the
ones
that
you
might
want
to
do
so
one
of
the
ones
we
get
talked
about
a
lot
is
the
rate
limiting
it's
on
up
on
the
left.
Here
I
can
pull
up
more
information
so
right.
So
there's
two
right
limiters
in
this
setup.
C
One
is
for
all
the
apis
that
the
browser
is
going
to
do
like
when
you're
logged
in
as
a
user
and
the
other
rate
limit
is
for
api
keys.
So
if
you're
scripting
to
a
server
you're
doing
lots
of
different
calls,
you
can
set
the
rate
limits
independently.
So
if
you
want,
if
you
don't
expect
to
have
any
api
key
calls,
there's
no
scripts
calling
the
server
you
could
set
this
low
to
make
it
a
little
tighter,
and
if
you.
C
C
So
that's
the
rate
limit.
So
that's
good
to
know.
If
you're
hitting
odd
problems
and
the
problems,
you
would
see
if
you're
hitting
this
they're
most
easily
seen
from
the
server
logs
you're
going
to
see
429
codes
and
you're
going
to
see
it
being
noisy,
saying
you
know
you've.
This
client
has
hit
too
many
requests
in
a
minute
and
yeah.
C
C
C
So
you
want
to
update
both
places
if
you're
running
into
these
timeouts,
depending
on
which
one
you're
hitting
right.
So
all
these
are
only
going
to
change
the
client
side.
So
if
you're
in
the
browser-
and
it
says
something
timed
out-
you
might
want
to
look
into
one
of
these
settings
to
bump
up
the
timeout
depending
on
what's
going
on,
and
then
you
also
might
need
to
bump
it
up
on
the
pier
if
it's
hitting
that
timeout
within
the
pure
process.
C
C
This
is
the
1-0
life
cycle
stuff
that
can
take
quite
a
bit
of
time,
depending
on
what
type
of
smart
contract
you're
running.
So
this
might
be
one
to
look
at
to
bump
up.
This
is
definitely
one
you
want
to
also
bump
up
on
the
pier,
because
it
has
its
own
timeout
for
letting
that
process
start
up
and
there's
one
for
joining
a
channel
so
appear
joining
to
the
channel
and
then
there's
one
for
installing
the
chain
codes.
C
C
So
one
is
installing
the
chain
code,
it's
a
different
operation
than
the
previous
one,
because
it
uses
the
lifecycle
chain
code
and
then
there's
another
one
for
getting
the
package
out.
So
you
got
those
two
options,
then
there's
kind
of
a
fallback
of
any
other
timeout
that
we're
using
there's
a
10
second
default.
For
that
one
and
one
more
setting
to
look
at
is
lockout.
C
The
lockout
limit
is
how
many
failed
password
logins.
You
can
have
before
that
ip
gets
blacklisted,
for
I
think
it's
only
five
minutes,
but
if
you
see
you
getting
four
or
ones
even
though
you
have
the
right
password,
you
can
see
it's
in
the
server
logs
that
you're
being
locked
out
and
if
you're
doing
dev
or
just
from
some
funky,
maybe
you
don't
care
to
have
a
lockout
limit.
You
could
bump
this
up
to
something
crazy.
C
B
B
Okay,
if
not,
there
is
a
next
topic
we
can
cover.
We
are,
which
is
local
development
right.
Some
people
have
asked
you
know
how
do
I
do
local
development
right?
That's
a
topic,
so
let
me
cover
some
stuff
on
that
right
because
you
know,
as
you
are
trying
things
and
doing
things
right,
you
know
that
may
come
in
handy.
I
know
a
couple
of
people
who
contributed
some
code
and,
and
you
know
it
would
be
nice
for
everybody
to
know
what
that
is
right.
B
So
if
you
look
at
the
repo
right
quickly,
the
repo
structure
right
so
within
the
console,
we
use
learner
right.
That's
like
a
you
know.
You
know
the
that
helps
with
managing
all
these
multiple
packages.
Right.
You
know,
when
you
have
a
mono
repo
kind
of
scenario.
There
are
multiple
components.
So
if
you
look
in
the
packages
is
where
the
main
components
are
right,
so
there
is
apollo
athena
and
state.
So
apollo
is
the
ui
component
right.
You
know.
That's
where
all
the
react
stuff
is
right.
B
If
you're
trying
to
develop
something,
you
know
if
you're
you
know,
if
you're
learning
react
or
good
with
react,
you
know
we
would
love
to
have
you
contribute
stuff
right,
so
so
it's
all
react-based
and
athena
is
the
quote-unquote
backend
of
it
right,
which
is
again
node
base
right.
It's
it's
a
it's
a
node
component
and
stitch.
You
know
we
won't
cover
too
much
right
now.
It's
slightly
advanced
I
feel
like,
but
you
know
what
it
is.
B
Is
it's
a
of
really
that
you
know
that
that's
converted
to
javascript
right.
You
know
that
is
a
process
where
the
products
get
converted
to
javascript
and
that's
how
we
talk
to
the
peers
and
orders
using
grpc.
We
don't
use,
you
know,
node
sdk.
We
don't
use
java
sdk,
we
have
our
own.
You
know
again
the
protocol
mechanism
using
javascript
everything
directly
goes
from
the
browser
to
the
backend.
Right
again,
you
know
it's.
B
We
will
schedule
a
different
call
for
that,
but,
but
you
know
just
be
aware
that
there
are
three
different
components
that
are
in
play
here.
Right
and
and
learner
is
the
one
that's
kind
of
stitching
things
together.
So
in
again,
if
you're
trying
to
do
local
development,
what
we
have,
if
you
go
to
the
end
of
the
you
know
the
readme,
you
see
a
couple
of
things
right,
so
you
know
you
use
you
install
learner
right,
that's
the
first
step
and
then
next
you
do
the
bootstrap
right.
B
You
know
you
know
it
will,
like
you
know,
basically
do
the
npm
install
under
the
covers
right.
You
know
you
do
the
clean
which
will
delete
it
and
then
you
do
the
bootstrap
and
then,
when
you
do
again,
if
you're
purely
doing
server,
side
development,
that's
athena,
of
course
right,
which
is
you
know
this
command
and
the
the
client
side.
I
mean
also
development.
If
you
want
to
do.
A
B
Then
then
it's
the
dev
apollo,
so
a
dev
apollo
would
run
the
you
know
again
live
react
and
then
it'll
also
start
the
server
it'll.
Have
it
all
set
up
when
you
do
that,
so
in
my
local
for
demonstration
purposes
right,
I
you
know,
I
started,
you
know,
learn,
run
dev
and
when
you
do
that
it
will
run
on
port
4002
and
again
it's
a
clean
console.
What
I
was
going
to
show
right
is:
how
do
I
know
the
components?
B
Where
do
I
get
those
components
to
be
imported
right
so
once
you
provision
then
started
the
components
right.
So
if
you
go
look
under
the
repo
under
there
is
a
work
area
right
and
you
should
see
assets
and
obviously
the
asset
to
be
imported
is
console,
underscore
assets
right
and
let's
just
pick,
you
know
it
is
ca
right
or
1
ca
and
what
we
see
inside
that
json
right.
This
is
the
generator
json.
B
Of
course,
when
you
read
on
the
whole
thing,
you
know
this
is
going
to
go
away
and
then
it
will
generate
a
new
one,
but
what
you
see
inside
is
these
endpoints
right.
So
it's
again
ca
underscore
or
one
because
that's
how
the
service
is
set
up
under
docker
docker
compose
right.
So
that's
how
the
network
is
known,
but
if
you're
doing
local
development,
where
you
have
consoles
running
locally,
you
want
to
be
able
to
reach
to
it
directly.
You
know
you
know.
C
B
You
would
change
these
to
localhost,
for
example
right,
so
you
change
those
and
then
what
I'm
going
to
do
just
for
demonstration
purposes
is
to
import
them
right
or
that
specific
one.
So
ca,
import
that
add
a
file,
and
you
know
within
the
work
area
assets
and
we
modified
the
file
under
certificate
authority
right
we
did
change
or
one
ca
and
then
import
it.
You
ignore
the
location
right
it
doesn't.
I
mean
you
can
choose
a
different
location.
B
You
know,
if
you
want
to
say
it's
open
shift
or
just
plain
kubernetes
or
anything,
that's
up
to
you.
It
doesn't
matter,
it's
just
display
purposes
really
right
and
then
that's
it
right.
So
the
component
got
imported
and
you
can
click
on
it
and
you
can
drill
down
and
say,
like
oh,
you
know,
I
want
to
generate
a
certificate
from
this
ca
right.
B
B
To
I
don't
know,
you
know,
change
the
you
know,
change
some
stuff
right.
You
know,
I
don't
know,
be
an
available
message
or
something
right.
So
I
go
somewhere.
It's
not
a
very
useful
demo,
but
you
know
I
just
want
to
demonstrate
that
you
can
change
it
and
the
changes
will
be
live
right.
I
don't
know
test.
C
B
Test
message:
so
it's
library
load,
so
you
can
quickly
do
development
and
check
it.
You
don't
have
to
go
through
the
whole,
build
and
all
that.
So
you
simply
start
that
endpoint,
the
learning
point-
and
you
know
you
can
you-
can
add
a
component
or
whatnot
again
the
source
code
wise
quickly
for
the
ui
again
right,
like
we
just
saw
it's
under
the
packages
apollo
and
then
you
have
all
the
source
code
right
under
components.
Right,
there's
a
ton
of
components.
You
will
see
right,
it's
hopefully
fairly.
B
You
know
self
describing
I
guess
right.
You
know
in
terms
of
the
names
and
what
they
mean,
but
you
can
of
course,
do
inspect
and
the
usual
things
people
do
with
the
react
development.
You
should
be
able
to
follow
and
then
identify
the
component
and
make
a
change
in
all
that
stuff
right
so
and
then
for
athena
again
same
things
applied
right.
So
there
is
a
file
watcher
that
goes
on
that
watches
the
file
changes.
So
it
should.
A
B
Then
you
know
you
should
be
able
to
see
the
changes
right,
so
that's
kind
of
like
so
all
the
ports
and
everything
just
to
mention
right
are
set
up
again.
The
config
file
david
was
showing
right.
You
know
the
under
env
under
athena.
There
is
a
dev
json
that
points
to
config
file
with
which
has
all
the
ammo
changes.
That
david
was
showing,
so
this
file
is
set
up
so
that
you
know
so
that
you
know
it
works
locally,
so
you
can
have
both
of
the
consoles
running.
B
At
the
same
time,
you
can
have
the
one
that's
provisioned
from
the
again
the
docker
image,
or
you
can
run
the
local
development
both
at
the
same
time
right
and
this
ui,
I'm
just
showing
was
connecting
to
the
test
network
right.
So
you
can
quickly
import
the
test
network
into
a
local
development.
Not
just
the
you
know,
doctor
based
one
and
then
then
develop
stuff
and
try
things
right.
I
think
that's
a
cool
thing
to
do.
Let's
see
what
other
questions
right.
C
B
B
A
Cool,
so
maybe
just
the
time
check
we
almost
top
of
the
hour,
so
thank
you
so
much
and
david
huffman
being
here
contributed
time
asking
the
question
so
so,
as
for
the
audience
plea,
please
go
go
ahead
to
the
meetup,
a
comment.
Leave
your
comments,
the
page
leave
your
comment.
What
topic
or
question
you
continue
to
type
there
so
we're
then
david
probably
can
pick
it
up
see
if
there's
a
future
section.
We
can
schedule,
certainly
like
where
you
mentioned,
there's
so
much
so
much
thing.