►
From YouTube: How to run a peer in devmode in Hyperledger Fabric
Description
A recording of the Tech Study Circle run by Hyperledger Sweden on January 29, 2021 where they walk through a comparison between the two paths to run a peer in devmode in #HyperledgerFabric. This is helpful in case you want to quickly test your #chaincode.
More about the event is at https://www.meetup.com/Hyperledger-Sweden/events/ctplzrycccbmc/
----
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 #HyperledgerMeetups #Blockchain
A
Okay,
so
welcome
to
this
hyperledger
sweden
meetup.
My
name
is
roland
and
I'm
happy
to
be
your
guest
for
today,
and
I
think
today
we
will
have
a
really
great
session,
and
this
session
is
so
that's
me
and
this
session
is
about
chain
code,
development,
environment,
and
this
is
a
comparison
between
the
binary
and
docker
version.
A
Here
you
find
our
agenda
in
the
slides
later.
I
will
post
this
slide
on
the
meetup
page
and
on
the
linkedin
page,
and
this
session
is
required.
You
can
also
watch
it
later
on
the
youtube
hyperledger
meetup
youtube
page,
and
here
I
have
some
collected
some
links,
so
here's
the
link
to
the
github
repository
the
support
material.
I
have
copied
this
also
in
the
chat,
so
you
would
like
to
follow
this.
Then
you
can
look
into
this
repository
to
see
all
the
steps.
A
What
is
needed
to
do
this
and
then
here
two
documentation,
links
to
hyperledger,
favorite,
documentation,
official
2.2
and
2.3
pha
code
def
mode.
So
it's
interested
interesting
that
in
the
2.2
version
you
will
not
find
this
in
this.
This
documentation,
this
tutorial
and
yeah.
So
it's
new.
Maybe
it
will
come
in
a
2.2
version.
I
don't
know,
and
then
here
I
will
find.
Then
you
will
find
the
medium
article
which
I
have
written
some
weeks
ago
about
this
topic.
A
Okay,
so,
let's
start
with
a
short
overview
of
this
pro
of
these
both
approaches,
and
so
in
this
session
we
are
going
to
talk
about
the
chain
code
development.
So
in
favorite
we
have
the
possibility
to
use
a
chain
code,
the
smart
contract
and
this
smart
contract
can
be
developed
in
different
languages.
A
This
is
a
new
one
in
the
2.2
version
and
it's
a
little
bit
different
to
the
old
shim
version
in
the
1.4
version,
and
this
is
an
abstraction
layer
which
gives
you
access
to
the
to
to
the
ledger
and
it
provides
an
api
and
with
this
api
you
can
interact
with
the
ledger.
So
that's
an
important
point
to
know
that
you
cannot
connect
directly
to
the
ledger.
A
A
A
That
means
that
you
have
you:
don't
have
to
use
the
docker
versions,
the
docker
version,
so
you
can
work
without
docker
and
on
the
other
side
you
have
the
docker
version,
so
you
can
make
a
docker
network
a
docker
compose
file,
and
then
you
can
create
a
dev
network
with
one
orderer
and
one
beer
and
then
or
with
a
couch,
to
be
database,
for
example,
and
so
on.
So-
and
we
have
two
approaches
here
and
when
we
compare
these
two
approaches
the
reason.
Well,
let
me
first
explain:
why
is
that?
A
So
why
is
this
important?
So
the
the
reason
is
that
when
you
use
a
chain
code
in
the
favorite
network,
then
you
have
to
especially
in
the
2.2
version
you
have
to
install
it.
You
have
to
improve
it
and
then
you
have
all
in
groups
collected.
Then
you
can
commit
to
this
chain
code
to
the
ledger
or
to
the
to
the
channel,
and
when
you
change,
when
you
have
a
change
to
this
chain
code,
then
you
have
to
upgrade
and
then
upgrade
process.
You
have
to
do
the
same.
A
So
this
has
an
yeah,
that's
a
little
bit.
That
comes
with
a
lot
of
effort
and
to
keep
the
way
short.
We
have
the
possibility
to
use
or
to
run
the
beer
in
the
so-called
death
mode.
And
that's
then
that's
the
the
reason
where
we
call
this
the
death
mode,
because
we
can
start
the
beer
in
a
special
mode
and
with
this
mode
we
can.
A
A
Maybe
in
go
today,
we
will
see
it
in
go
and
then
you
can
build
the
chain
code
and
then
you
have
to
start
the
chain
code
container
again
and
you
can
test
the
chain
code
directly
against
the
beer
with
a
cli
command
and
that's
the
reason
why
we
need,
from
the
developer
perspective,
a
way
to
test
to
do
a
fast
test
on
our
on
our
smart
contract.
And
when
we
compare
this,
we
see
that
in
the
binary
version
we
need
a
lot
of
terminal
windows
so
oops.
A
So
we
can
use
ssh
terminal
windows
for
that
or
we
can
use
terminal
multiplexer,
for
example,
so
that
we
have
one
ssh
terminal
to
the
machine.
And
then
we
have
some
panels
inside
of
this
mox
terminal
emulator
and
for
the
binary
version.
We
need
four
different
terminals,
and
so
these
are
some
key
effects.
I
have
collected
to
compare
this,
both
approaches.
So
in
the
binary
version
we
need
the
one
more
terminal
and
in
the
docker
edition
we
need
only
three
terminals
and
so
in
the
binary
version
we
have
here.
A
I
have
a
point
here:
correct
environment
variables
are
important
so,
and
this
is
an
important
point
to
understand.
When
you
use
docker
and
you
start
the
docker
container,
then
this
is
an
isolated
room.
So
that
means
that
when
you
use
a
part
for
example,
then
you
could
use
the
same
part
on
this
docker
host
again
and
because
it's
isolated
in
the
docker
container.
A
A
You
will
find
it
and
to
get
rid
of
this,
we
have
to
manipulate
the
we
have
to
use
the
the
correct
environment
variables
so
that
we
can
place
the
blockchain
data
and
and
all
other
variables
which
we
could
need
to
create.
The
binary
development
version
which
will
run
on
this
machine,
and
one
important
point
is
that
we
have
an
official
guide
in
there
in
the
hyperledger
documentation,
hyperletrophyllic
documentation.
A
A
And
when
you
compare
this
processes,
then
you
see
we
have.
We
need
some
terminals
for
this,
as,
as
I
have
mentioned,
and
then
the
green
ones.
Are
there,
the
the
binary
versions
and
the
blue
boxes
here
are
the
process
of
the
docker
version,
and
you
see
that
we
can
have
so
in
terminal.
One
first
is
that
we
have
to
download
the
official
favorite
ripple
repository
so,
and
this
is
a
part
which
you
you
need,
and
this
is
and
this
step
is
not
needed
when
you
use
the
docker,
the
docker
version.
A
And
then
when
you
have
this
fabric
repository,
then
you
have
to
build
this
binaries
so
to
build
this
binaries.
You
need
this
go.
This
is
the
by
all
the
oil
program.
Spear
order,
config,
tx
scan
and
other
tools
are
built
in
written,
go
and
then
we
have
to
build,
go
binaries
for
that,
and
we
have
also.
We
need
also
some
build
tools
to
build
the
spinals
and
it's
a
preparation
step
and
for
the
docker
composition.
When
we
use
this
in
a
docker
version.
A
So,
and
here
we
have
and
yeah
so
that's
a
little
bit
different
in
the
approach
and
then
the
the
steps
are
the
same,
so
the
first
step
is
the
next
that
are
the
same.
So
the
next
step
is
that
we
create
the
genesis
block
for
this
test
network.
This
is
a
step
which,
which
we
have
to
do
in
both
versions,
and
then
we
can
start
the
order
in
the
binary
version.
A
A
A
So
these
are.
These
are
the
steps
until
here
in
terminal,
slide
and
terminal
2.
We
have
to
start
the
docker
conte,
the
the
peer
and
the
we
have
to
start
appear
with
a
special
option
here,
and
this
option
is
called
peer
chain
code,
dev
chain,
code,
dev,
and
when
we
start
this
in
the
in
the
terminal,
then
we
can
create.
Then
the
terminal
is
also
blocked.
So
and
then
we
have
to
create
and
draw
in
the
channel
in
terminal
free
here.
A
So
we
have
to
create
the
the
channel,
and
then
we
join
the
channel
and
yeah
and
in
this
terminal
three
we
can
start
and
stop
the
chain
code
yeah
manual.
But
in
the
first
time
when
we
start
the
chain
code,
we
have
to
make
all
the
steps
to
install,
approve
and
commit
the
train
code.
But
only
for
the
first
time-
and
this
is
the
process
for
version
2.2.
A
When
you
have,
when
you
use
version
1.4,
then
you
will
not
have
this
chain
code,
lifecycle
policy
and
there's
the,
but
the
process
is
the
same,
but
it's
the
same.
How
you
do
it
in
the
1.4
version,
but
the
process
to
install
the
chain
code
is
a
little
bit
different
and
then
and
for
the
docker
version
we
can
in
terminal
2.
We
can
create
and
join
the
channel,
and
then
we
can
start
and
chop
the
start
and
stop
the
chain
code
in
this
terminal
as
well.
A
Yeah
so,
and
here
I
have
a
disapproved
process,
so
we
have
to
do
this
approved
process
only
once
so
for
the
first
for
one
time
and
then
we
can
use
the
ca
cli
commands
to
use
so
beer
chain.
Query
and
beer
be
a
query
and
be
invoked
to
test
our
chain
code
here
and
for
the
binary
version
yeah.
We
need
one
terminal
so
and
that's
why
the
because
in
terminal
the
dermal
one
is
blocked
through
the
order.
A
A
A
A
A
We
need
the
query
armor
file
and
then
here
membership
service
provider
folder
with
with
the
crypto
material
for
the
fedex
test
case,
and
then
what
I
will
file
as
well
so
and
this
folder,
this
information
we
can
use
and
the
second
important
folder
is
the
build
folder
and
there's
a
pin,
pin
folder
inside
and
there
we
will
have
appear
in
order
and
then
config
dx
game
file.
So
but
this
will
this
this
free
binary,
this
three
binary
files
will
be
created
when
you
build
when
you
build.
A
A
Yeah
so
one
question
here
in
the
chat,
so
when
we
follow
official
doc,
we
use
binary
approach.
Yes,
so
in
this
in
the
official
documentation,
you
have
this
binary
approach,
but
when
you
think
about
it
about
this
a
little
bit
so
with
this
binary
approach,
you
can
do
much
more.
So
you
can
also
say:
okay,
we
create
a
network,
a
docker
composition
network,
and
then
we
create
on
a
second
machine
appear
which
runs
as
a
binary
version,
and
you
don't.
A
So,
for
example,
when
you
have
a
logging
application
or
where
you
have
to
create
a
lot
of
data-
or
I
don't
know-
and
then
you
can
and
you
take-
must
take
care
on
performance
for
example,
then
you
can
decide
to
create
the
network
where
you
have
the
binary
version.
Maybe
it's
a
little
bit
faster
and
you
need
less
resources
because
of
the
fact
that
you
don't
need
a
docker
system
for
it,
and
then
you
can
use
also
the
binary
version
as
well.
A
But
we
also
use
docker
there.
I
don't
know
this.
I
don't
understand
this
question,
so
you
have
to
you
have
to
choice.
You
can
use
both
and
in
the
end
you
have
to
decide
which
version
is
the
best
for
you
in
this
presentation
today
you
will
see
both
version
and
then
you
can
decide
what
is
the
best
fit
for
yourself?
A
A
And
then
I
have
created
a
simple
structure,
so
I've
created
the
folder
with
artifacts,
so
it's
empty.
Then
I've
created
the
chain
code
folder
with
my
chain
code.
So
this
is
the
place
where
my
chain
code,
my
go.
Files
from
the
train
code
lives.
So
here
the
s
as
a
simple
asset
chain
code.
We
will
use
it
later,
so
I
have
copied
this
from
the
favorite
samples
and
then
we
will
use
this
so
here
we
need
a
place
where
we
can
put
our
chain
code
and
interact
with
it
and
then
we
need.
A
Later
I
will
create
a
data
folder
and
with
this
in
this
data
folder,
the
blockchain
will
be
stored.
So
this
is
the
place
where
we
store
the
blockchain,
it's
also
empty.
For
now
so,
and
so
that's
a
simple
structure,
you
can
name
it
how
you
like
and
yeah
so
and
then
we
have
this
so,
and
the
first
step
is
always,
but
we
have
to.
We
have
to
put
this
path
here
into
the
path
so
that
we
can
call
p
order
and
config
tx
scan.
A
A
A
A
So-
and
you
see
here,
the
configuration
of
this
sample
gap
mode
so
so
and
there
are
other
configurations,
so
you
can
look
into
this
file,
and
so
here
you
have
the
profile
section
and
then
you
have
here
different
configuration
samples.
So
it's
also
useful
from
the
administrator
side
to
look
into
this
configurations
and
see
how
you
can
use
the
different
configurations,
but
from
the
developer
side
we
have
here
a
ready
to
use
profile,
and
this
is
the
configuration
also
with
the
proper
endorsement
policy
here.
A
But
it's
not
important
here,
because
it's
only
for
for
testing.
So
the
only
thing
is
that
it
works
that
you
can
use
the
chain
code
with
the
cli
commands.
So
but
the
important
part
is
this
profile
is
ready
to
use
and
that's
why
we
use
it
here
and
then
we
have
to
create
the
system
channel
and
again.
This
is
block
and
yeah
and
the
place
where
we
create.
This
is
our
artifacts.
A
A
We
can
use
this
in
two
ways,
so
we
can
export
these
three
ottawa
environment
variables
or
we
can
use
it
also
in
a
single
command
line.
So
I
for
copy
and
paste.
I
use
this
single
version,
single
command
version
and
so
for
the
to
for
a
better
understanding.
So
it's
often
better
that
we
can
use
this
expert
command
and
then
we
have
to
have
see
we
have
seen
you
can
see.
The
single
variables
are
in
in
a
single
way.
So
it's
easier
to
understand
so
and
we
need
three
of
them.
A
So
we
need
the
place
where
the
genesis
block
lives.
Then
we
need
the
location
from
the
file
ledger,
so
it's
it
should
be
in
our
data
data
fall
in
our
data
folder
and
this
data
order
folder
and
then
we
need
the
again.
This
is
profile
type,
so
that's
the
sample
depth
module
and
then
we
can
start
this.
No,
we
will
do
it
so
we
use
so
we
need
different
terminals,
and
here
I
have
some
helpful
trucks,
operations
commands
and
I
will
try
it
here
with
this.
So.
A
So
and
you
see,
the
roi
is
running
and
the
terminal
is
blocked,
and
now
we
need
the
new
panel,
so
we
can
do
this
with
ctrl
b
and
quotes,
and
then
we
have
splitted.
This
terminal
here
into
this
is
a
little
bit
tricky.
So
it
depends
a
little
bit
on
the
keyboard,
so
you
have
to
practice
this
a
little
bit
and
then
yeah
it
works.
A
A
Start
we
have
to
start
the
dpo
and
for
the
peer
we
need
also
some
environment
variables.
So
we
need
this
core
operation.
Listen
address
the
file
system
path,
it
should
be
in
onto
the
data
folder.
Then,
okay,
the
logging
is
not
so
important,
but
we
can
do
it
and
then
the
chain
could
listen
address
and
of
course
the
important
command
is
here,
be
a
node
start,
and
then
we
have
here.
A
Make
the
panels
a
little
bit
larger,
so
we
have
an
ordering
session.
We
have
at
a
panel
where
the
peer
is
running
and
then
we
have
to
create
the
channel
so
and
for
the
channel
we
have
to
create.
We
have
to
use
the
config
exchange,
dx
gen
file,
and
so
I
call
the
channel
channel
one
and
in
the
artifacts
artifacts
folder,
we
will
create
this
channel
creation
transaction
and
we
use
also.
A
A
A
A
A
A
A
A
A
A
A
Then
we
have
to
approve
the
chain
code,
then
commit
the
chain
code,
but
this
step
we
have
to
do
only
once,
and
these
are
the
standard
steps
to
install
a
chain
code
in
the
2.2
version
through
this
new
lifecycle
chain
code,
environment
policy
or
governments-
and
this
is
a
command
beer
lifecycle
chain
called
approve
org,
then
we
can
check
this
check,
commit
readiness,
and
then
we
have
to
commit
this.
So
we
need
to
approve
this
from
organization
from
us
sample
organization.
A
A
A
A
Get
message
to
you
say
hello
to
here:
okay,
so-
and
this
is
how
this
works
so,
but
what
happened
when
you
change
this
chain
code?
So
then
you
have
then
again
you
have
to
stop
the
chain
code
itself
so
and
we
can
do
this
when
we
switch
back
in
this
in
this
panel
ctrl
d
coup,
you
see
the
numbers
control
be
cool.
A
So
maybe
we
will
put
this
here.
So
we
have
changed
the
chain
code.
We
have
the
import
for
the
os,
so
okay,
so
now
we
have
added
the
debug
value,
but
only
the
asset
name.
The
queried
asset
name
should
only
be
displayed
when
we
deliver
the
special
environment
variable
depth
mode
enabled,
for
example,
when
it's
not
is
is
equal.
It's
not
equal
to
zero
here,
and
so.
But
the
important
point
here
is
that
we
change
the
chain
code
now
and
now
we
want
to
test
if
this.
A
So
we
can
build
this
chain
cut
again
and
then
we
can
start
it
and
we
can
start
the
chain
code
with
the
same
command
and
we
have
here
the
enable
test
mode.
So
we
have
here
in
this
single
line
command
also
the
environment
variables,
and
we
want
that
only
when
this
death
mode,
enviro,
death
mode,
enabled
environment
variable
is
delivered
to
this
chain
code
and
it
has
a
random
value.
A
A
A
A
A
A
So
that's
the
reason
why
I
have
this
here
so
control
p
and
then
on
the
mac,
tester
20
function
and
the
up
or
down
keys,
and
then
you
come
in
a
scroll
mode.
I
think
the
scroll
mode
and
you
can
then
you
can
scroll
up
and
down
and
yeah
to
leave
this
mode.
You
have
to
use
the
escape
key,
so
this
works
on
a
mac
keyboard.
So
I
don't
know
how
is
this
on
there
on
the
windows
or
the
other
keyboard?
A
A
A
This
is
an
example,
then,
in
some
chain
code
folders
here
you
find
the
go
version.
Java
version,
javascript
version,
typescript
version,
but
not
every
example-
has
all
languages
implemented.
So
this
marvel's
example
has
only
the
go.
The
gold
chain
code
here-
and
you
see
here
the
meta
in
file
meta
in
folder,
and
that
means
that
the
the
couchdb
couchdb
is
involved
because
we
have
here
the
index
owner
json
file.
This
is
needed
when
you
want
to
use
a
couchdb
instead
of
level
level
db
yeah.
A
A
Demonstration
chain
code
here
also
with
tests
with
go
tests
here,
yeah,
and
then
you
find
also
here.
This
is
the
chain
code
yeah
when
you
have
in
java
and
javascript
and
so
on,
and
you
have
your
also
the
in
the
application
folder
and
then
the
application
file
folder.
You
find
here
the
javascript
or
better
nodejs
version
of
the
for
the
client
from
the
client
side,
and
this
is
needed
to
connect
to
use
the
the
chain
code
without
the
cli
command.
A
So
cli
command
is
only
for
testing
and
for
the
administ
administrator
part
and
the
javascript
client,
the
nodejs
client.
I
think
it's
the
standard
language
for
the
for
for
the
client
side,
and
here
you
find
how
you
can
interact
with
an
app
chair.
So
this
is
the
an
expressjs
version.
I
know
this
is
oh
no.
This
is
also
a
cli
version,
but
you,
you
find
all
the
commands.
You
need
to
submit
the
transaction
and
here
evaluate
to
query
a
transaction,
and
you
find
here
samples
so
and
here
you
find
all
the
chain
cons.
A
A
A
This
is
a
new
version
of
this
level
of
abstraction
and
I
think
maybe
that's
the
reason
why
they
have
this
put
this
here
on
the
side
and
on
this
first
level,
so
maybe
that
all
people
see
that
this
is
new
and
yeah
and
then
the
chain
code
here
the
chain
code
folder.
These
are
examples.
This
examples
exists
also
in
1.4
version.
A
So
and
when
we
look
at
the
sac
here,
then
you
have
here
the
shim
implementation
and
that's,
I
think,
maybe
that's
I
don't
know
I.
I
I
not,
I
don't
know
why
this
fair
example
structure
is
like
it
is,
and
I
think
this
is
because
this
is
the
old
version.
So
all
this
this
apache
a
buck
is
also
an
interesting
example,
because
this
is
in
this
example.
It's
also
based
on
the
shim.
Ask
him-
and
this
is
an
asset
attribute
asset
attribute.
A
Chain
code
example,
I
think
so
so
in
this
example,
attribute
based
access
control.
This
is
the
the
right
term.
So
this
is
an
example
for
an
attribute
based
access
control,
chain
code,
and
with
this
you
can,
when
you
make
a
transaction,
then
you
have
to
use
a
certificate
from
a
user,
and
this
user
can
have
some
properties
and
with
the
chain
code.
A
You
can
read
this
properties
with
this
here
and
then
you
can
say:
okay,
when
this
certificate
has
the
property,
maybe
a
group
or
department
development,
then
you
can
write
in
the
chain
code.
You
can
use
the
white
function
or
the
the
the
store
function,
the
put
function,
for
example,
and
when
you
a
user
which
belongs
to
the
marketing,
for
example,
then
your
certificate
has
the
attribute
marketing
or
something
like
that.
And
then,
when
this
user
tried
to
use
this
function,
then
the
you
you
will
receive
an
error,
for
example.
A
A
A
So
this
is
this-
is
the
this
is
standard
go
language
so,
and
so
you
have
to
look
into
the
go
documentation
to
understand
what
the
first
parameter
and
the
second
parameter
here
means
so
and
yeah,
but
you
find
your
other
examples
as
well.
So
the
commercial
paper
is
also
a
good
example
where
you
find
helpful
tools.
For
example,
one
important
point
is
here:
the
under
organization's
application,
so
here
the
add
to
wallet
script
here.
A
This
is
very
helpful
here,
so
we
need
the
when
you
use
this,
this
nodejs
application
and
then
you
connect
to
the
fabric
network.
Then
you
need
the
user
and
this
user
profile
all
these
user
credentials.
This
identity
is
stored
in
the
wallet
and
then
you
have
to
enroll
and
create
a
new
user.
But
this
is
only
possible
when
you
have
been
fed
x-ray
running
and
in
this
development
environment.
A
A
And
in
a
default
configuration
two
users
are
created
in
admin,
user
and
the
user
one
and
with
this
script
or
with
the
source
code
here
in
this
script,
so
I
think
you
can
use
it.
But
you
have
to
change
the
paths
here.
Then
you
can
convert
the
user
one,
two,
a
wallet
identity
which
you
can
use
in
for
your
nodejs
application
and
and
that's
an
helpful
cli
tool
to
convert
an
existing
identity
to
to
the
wallet
in
your
for
your
client
application.
A
So,
and
it
makes
sense
to
look
through
these
examples
here-
and
you
see
here
a
lot
of
examples
where
you
can
learn
to
do
different
things
here
from
this
from
the
shell
scripting
side
from
the
chain
code
side
from
the
go
side,
java
side
and
so
on.
So
a
lot
of
best
practice
examples
here
and
you
can
find-
and
you
can
look
what
what
is
a
good
solution
for
yourself.
A
Okay,
so
yeah.
This
is
the
the
a
short
side
note
on
the
different
chain
codes
here,
so
you
can
copy
all
these
chain
codes.
All
my
examples
are
mostly
from
this
official
documentations
here
from
your
favorite
samples
here,
okay,
so
now,
let's
move
forward
and
go
to
the
second
example-
and
this
is
the
example
with
the
docker
version
so
and
for
this
we
need
a
docker
composition.
A
A
A
We
have
basically
the
same
structure.
We
have
an
artifacts
folder
with
a
chain
code
folder
with
the
simple
as
a
chain
code
example.
Here
we
have
a
folder
with
ledger
data
so
and
then
we
have
here
the
sample
configuration.
This
is
the
same
sample
configuration
we
have
used
before.
So
I
have
copied
in
here
this
into
this
in
this
folder,
and
then
we
have
a
docker
composition.
A
Here
with
an
order
and
appear
so-
and
we
need
this
end
file,
don't
forget
on
don't
forget
this
environment
file,
so
it
is
dot
infile.
These
are
environment
files
for
the
docker
composition
and
yeah.
So
it's
basically
a
little
bit
copy
and
paste
from
the
test
network
from
the
official
test
network
and
yeah.
A
So
basically
the
process
is
the
same
and
we
need
the
same
elements,
but
the
configuration
is
a
little
bit
different.
So
when
you
are
more
familiar
with
docker,
then
you
are
fine.
If
you
use
the
docker
version
and
when
you
are
not
so
familiar
with
docker
when
you
do
it
a
little
bit
more
with
the
binary
versions
or
works
with
the
binary
versions,
then
you
can
do
the
other
way
so
and
important
here
is
what
is
important.
So,
okay,
here
I
mean
for
the
order
config
configuration.
A
We
need
the
same:
the
sample,
config
membership
service
provider
folder.
Then
we
need
the
genesis
block
and
we
need
the
place
where
the
auto
puts
his
his
data.
His
ledger
data-
and
we
mount
this
into
the
container
here
so-
and
that
is
what
I
have
meant
before.
When
you
use
the
docker
version,
you
don't
sometimes
you
don't
recognize
where
all
this
data
lives,
because
you
mount
a
folder
to
a
path.
A
So
and
also
this
path
is
on
your
local
machine
so
and
that's
important
to
know
that
you
have
then,
when
you
use
the
binary
version
of
persistent
version
and
the
files
are
stored
in
this
location
here
and
yeah
yeah
and
for
the
beer
the
same
here
yeah,
so
the
gossip,
for
example,
gossip
bootstrap.
We
don't
need
this
because
we
only
have
one
pier
here
and
the
volume
here
also
here
only
the
ledger
data.
So
you
see
here
we
mount
this
on
bar
hyperledger
production.
A
So
and
then
here
the
command
important,
you
see
bigger
chain
code.
Def
is
true,
okay,
so
there
is
this
and
yeah
and
then
the
sample
config.
So
yes,
here
we
can
look
into
this.
That's
the
same.
I
have
shown
before
important
here.
Are
the
profiles
yeah
and
you
see
here
and
that's
also
a
good
place
to
learn
how
you
can
set
up
your
profiles
in
different
configurations?
A
A
A
And
when
you
try
to
address
this
address
here,
then
yeah
you
mean,
then
this
is
your
variable
name,
so
you
have-
and
this
is
the
prefix
you
can
say
it's
a
prefix
okay,
so
they
said
all
variables
all
values
here
in
the
from
the
beer
section,
have
the
prefix
core
beer
and
then
listen
address
network
id
chain
code
address,
for
example,
here
and
so
on.
So
you
can
address
all
this
all
this
configuration
values
with
the
environment
variables
here
with
the
same
schema
so
and
for
the
order.
A
A
A
A
A
Okay,
so
and
yeah,
and
the
steps
are
here
so
we
don't
have
to
so
we.
The
only
thing
is
what
we
have
to
do.
Is
we
create
a
folder
with
this
small
subfolders
we
have
to
create.
We
have
to
copy
this
sample,
config,
yeah
and
the
environment
value
and
this
end
file,
and
then
we
can
copy
also
the
docker
composition
from
the
test
network.
A
So
and
then
we
mod
we
can
modify
this
blah
blah
blah
saw
this.
You
have
seen
yeah
docker
network.
This
is
the
same
name
and
then
customize
the
rocker
compose
file.
So
we
have
to.
We
need
only
the
order
and
the
beer
here
and
yeah,
and
we
have
to
change
the
other
endpoints
here,
okay,
so
and
so
and
that's
it
and
then
we
can
create
the
artifacts.
So
we
have
to
set
the
environment
variables
for
this
new,
and
so
let's
check
if
this
is
empty.
A
A
A
A
A
A
A
We
can
use
here
for
ssh
terminals,
and
then
we
have
a
little
bit
more
comfort
in
the
case
of
scrolling.
But
the
good
thing
of
the
trucks
terminal
is,
we
can
leave
our
terminal
and
without
stopping
the
system.
So
we
can
detach
from
this
truck
session
and
then
we
can
log
out
from
the
terminal
and
tomorrow
we
can
come
back
and
then
we
can
reattach
to
this
session
and
all
this
running
and
that's
the
good
thing
of
the
terminal
multiplexer.
A
A
A
A
A
A
A
A
A
A
A
A
A
A
Okay,
so,
and
then
I
say:
okay,
I'm
fine
here
today
and
now
I
have
to
leave-
and
now
we
can
say,
control,
p
d,
and
now
we
have
detached
us
from
the
session,
and
now
we
can
close
this
terminal
and
that's
it.
But
in
the
background
the
development
environment
is
still
running
and
we
can
look
with
chmark's
ls.
A
Here
this
is
an
ubuntu
box
which
is
running
on
digital
ocean
and
the
blockchain
is
also
running
on
digitalocean
and
on
my
local
machine.
I
only
use
a
visual
stud
visual
studio
code
editor
and
I
use
the
ssh
favorite
extension
ssh
extension
and
I
connect-
and
I
can
connect
directly
to
my
virtual
machine
on
in
the
cloud
and
I
can
work
here
as
it
as
it.
A
I
would
work
on
my
local
machine,
but
I
don't
have
to
install
anything
on
my
machine
here
and
I
think
that's
a
really
cool
developer
environment
so
and
we
don't
so
you
can
do
it
also
on
windows
as
well.
So
when
you
work
on
windows,
you
can
also
use
visual
studio
code
with
the
ssh
extension,
but
you
can
use
the
linux
environment
and
you
don't
have
problems
with
file
names
and
file
pops
and
something
like
that,
and
I
think
that's
a
pretty
cool
environment
here.
A
So,
okay,
of
course-
and
you
can
hear
different
versions
of
chain
code,
so
the
system
is,
is
the
same.
So
when
we
say
we
have
a
ledger
and
then
we
have
a
channel
and
on
this
channel
we
have
installed
different
chain
codes,
so
you
can
have
you
can
test
also
a
second
chain
code
in
this
configuration
to
the
same
time,
because
we
can
install
on
the
channel
different
chain
codes
and
yeah.
So
it's
depends
on
you
and
on
your
fantasy,
how
you
can
organize
your
development
environment
here?
A
Okay,
so
is
there
something
interested
here?
Okay,
no
yeah.
So
I
think
I'm
now
on
my
end
and
yeah.
So
today
you
have
seen
two
possible
approaches
how
you
can
easily
test
your
chain
code.
You
can
use
the
binary
version
to
this
version.
You
will
find
your
official
look.
You
will
find
official
documentation.
A
A
A
That
is,
I
don't
think
so,
but
this
is
a
question
I
have
tackled
a
while,
but
some
I
found
some
scripts,
but
I
think
that
will
not
work.
So
when
you
restart
the
machine,
I
don't
want
to
say
it
will
not
work.
So
some
cool
guy
has
found
I'm
sure
some
cool
guy
has
found
a
solution
for
this,
but
normally
this
max
session
is
lost
when
you
restart
your
machine,
so
you
have
to
make
a
script,
and
I
I
think
I
can
remember.
A
We
have
already
a
slack
channel
and-
and
you
can,
I
think
I
could,
if
you
want,
I
can.
I
could
post
the
invitation
link
here
in
this
chat
and
in
this
slack
room
in
this
slack
channel.
You
can
ask
your
questions,
but
I
have
to
say
at
this
time
there
is
no
much.
There
is
not
so
much
traffic
in
this
in
the
in
this
like
channel
so
but
yeah.
So,
but
we
have.
A
A
A
A
Yes,
so
I
will
see
so
for
the
next
very
next
session
I
have
planned,
maybe
that
maybe
they
put
a
good
idea
so
for
the
next
session,
I
have
planned
a
comparison
between
so
it's
about
the
keys.
So
when
we,
when
we
query
something
when
when
we
store
something
in
the
in
the
blockchain,
then
we
need
the
key
so
and
the
value
that's
that's
all
so
to
store
anything
in
favorite.
We
need
the
key
and
the
value.
A
A
But
when
we
use
this
key,
then
we
can
query
an
asset
into
the
into
the
blockchain,
but
the
key
is
a
string,
so
it
depends
on
the
used
state
database.
So
when
we
use
a
level
db
as
a
database
as
a
state
database,
then
we
can
only
query
the
key
or
a
composite
key
or
a
key
range.
So
and
the
interesting
part
is
the
composite
key
and
we
cannot
make
in
there
in
the
level
db,
which
query
or
to
query
a
property
from
the
asset,
for
example.
A
So
when
we
need
when
we
have
a
use
case
where
we
have
to
query,
when
you
look
at
the
car
example
or
the
fab
car
example
there,
you
have
colors,
for
example,
a
property.
It's
called
color
and
you
want
all
red
cars
to
create
all
red
cars.
Then
you
cannot
do
this
with
the
with
the
level
db,
so
you
have
to
do
couchdb
and
when
you
use
couchdb,
then
you
can
make
which
queries
and
all-
and
you
can
do
all
the
queries
which
couchdb
has
so
you
can.
You
can
use
aggregation
functions.
A
You
can
use
whatever
every
query
you
can
do
in
couchdb
and
and
maybe
in
the
next
session.
I
would
like
to
show
how
this
fits
together
and
how
we
can
use
a
composite
key
to
query
some
data,
because
I
used
this
composite
key
in
a
project
last
week
and
then
I
was
thinking
okay.
This
is
a
good
example
to
use
the
the
prototype,
the
the
composite
key,
and
then
I
observed
that
we
cannot
query
a
partition
part
of
the
composite
key,
so
you
have
to
use
always
the
the
prefix
from
this
composite
key.
A
So
you
can.
That
means
that
you
cannot
query.
When
you
have
a
composite
key
which
is
established
with
three
parts,
then
you
can
not
query
only
the
last
part
of
this
composite
key,
so
you
have
to
query
the
whole
key,
so
you
can
only
query
part
one.
You
can
create
part
one
and
two
and
then,
and
one
and
part
one
two
and
three,
so
you
only
and
you
cannot
clearly
depart
but
free
alone.
So,
for
example,
and
that
was
an
and
a
new
a
new,
a
new.
A
Impact,
no,
I
don't
know
so.
This
was
an
that
was
really
new
to
me
and
so
and
this
I
think
this
is
a
good
example
how
you
can
to
to
explain
how
things
are
stored
in
favic
and
how
we
can
query
this
and
we
don't
store
keys
in
database
right.
We
don't
store
keys
when
you
think
when
you
mean
with
keys,
credential
keys
or
certified
certificates.
A
Yes,
so
in
the
database
you
don't
store,
but
that's
not
true,
so
you
can
store
the
keys
also
in
the
database
yeah.
They
are
because-
and
there
is,
I
think
this
the
example
for
this
is
also
in
the
fair
examples,
and
this
example
is
the
I
think
commercial
example
and
we
can
use
no,
no,
no
I'm
wrong,
not
the
key,
so
part
keys.
A
So
when
we
use
the
client
application,
we
need
a
local
wallet
and
in
this
local
wallet
we
need
the
private
key
and
some
credentials
from
the
user
and
this
keys.
We
can
store
in
in
a
database
so
and
we
can
store
it
also
in
the
memory
because
we
can
use
different
wallets,
so
we
can
use
a
wallet
for
the
fi
as
a
file
wallet.
A
You
know
in
the
folder
we
can
use
a
wallet
in
the
memory
and
with
this
in
the
memory
we
can
use
also
a
wallet
in
a
mysql
database,
for
example,
or
in
a
prosperous
database.
So
and
this
example
is
with
a
postgres
database.
I
think
I
saw
this
on
the
official
ibm
site
or
in
the
commercial
paper
site.
So
but
it's
a
difficult
questions,
but
when
you
mean
you
want
to
store
your
keys,
your
your
certificates
and
then
you
don't.