►
From YouTube: Cloud Foundry Community Advisory Board Call [June 2019]
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Next
week,
sorry
next
month,
yeah
yeah
I
was
distracted.
So
what
we'll
do
is
the
typical
things
will
get
an
update
and
then
from
the
different
PMC's
and
also
from
chip
and
then
we'll
give
dr.
Nick
Williams.
All
the
time
in
the
world
he's
been
playing
with
sidebars
and
I.
Guess,
bill
packs
or
bill
packs
with
site
cards.
I,
don't
know
something
like
that
should
be
fun.
As
you
know,
what.
C
Yeah
yeah,
hey
I'll,
just
highlight
a
couple.
I,
like
you
said
you
know,
there's
a
bunch
of
stuff
in
the
agenda
to
two
things
that
are
worth
highlighting.
You
summit
schedules
going
live
tomorrow,
which
is
great.
That
should
be
a
lot
of
fun
and
the
other
thing
that
all
I'll
highlight
is
that
there's
the
contributor
summit
that
we're
having
tied
to
the
larger
CF
summit,
that's
going
to
be
on
September
10th,
starting
at
9:00
in
the
morning
right,
so
not
don't
arrive.
C
If
you
plan
to
come
to
the
contributor
summit,
don't
arrive
on
the
10th
in
the
afternoon
visual
it
missed
it.
We
did
that
as
an
experiment
in
the
North
America
event
back
in
April.
It
seemed
to
go
fairly
well,
but
we
also
learned
a
lot
and
we're
gonna
iterate
a
bunch
on
the
format
thanks
to
Yui
and
Eric
and
Marco
and
Matt.
C
C
Yeah,
so
let
me
let
me
give
some
context
on
that.
One
of
the
one
of
the
things
that
we've
recognized
is
that
the
the
CFS
membership
right,
the
individuals
that
represent
the
companies
that
provide
a
lot
of
the
funding,
maybe
don't
necessarily
understand,
for
example,
know
that
the
events
run
generally
at
a
small
loss
or
breakeven
right.
So
what
we
wanted
to
do
was
to
make
sure
that
there's
a
little
bit
more
conversation
about
the
reality
of
the
the
organization
and
kind
of
feel
how
how
things
are
working
where
things
can
improve.
C
So
it's
we've
had
two
of
them.
So
far,
it's
generally
sent
out
to
the
official
contacts
at
the
various
member
companies,
but
you
know
if
you
would
like
to
join
the
next
one
you
can
reach
out
to
Bri,
as
noted
there
we'll
make
sure
the
year
you're
added
to
the
list.
So
you
can
see
it.
You
know
join
in
and
be
part
of
that
conversation.
C
So
it's
less
about
the
technology
and
it's
more
about
the
the
cff
organization
itself
and
dr.
max
I
think
you
were
gonna
hit
some
of
these
other
ones
too.
All
I'll
toss
those
out
yeah,
dr.
Nick,
inspired
inspired
us
when
he
offered
to
provide
a
few
awesome
videos
and
we
to
have
other
videos
like
that
published
in
the
the
Cloud
Foundry
YouTube
accounts.
So
it's
a
cool
opportunity.
If
you
actually
want
to
record
a
new
feature
that
you've
built
or
really
I
think
a
lot
of
the
demos
that
are
shown
off
an
app
call.
C
You
know
if
there
were,
if
there
tightened
up
and
shortened,
they
could
become
a
pretty
interesting
informational,
video,
we'd
love
to
have
those
as
well
so
again,
BRE
breeze
your
lady
she's
got
a
publishing
guide
pulled
together
for
that
and
I
would
love
to
have
loved
to
have
more
material
up
there.
So
those
are
probably
the
two
big
new
ones.
There.
A
C
Dr.
max
yeah
thanks
dis
mention
a
few
highlights
from
the
past
month
or
so
within
the
run
time
GMC.
As
usual,
we've
had
some
CF
deployment
releases.
Think
our
latest
CF
deployment
was
nine
three,
oh
and
as
mostly
bumping,
the
component
releases
for
a
new
functionality,
but
I
think
that's
also
fixed
a
few
things
around
component
metrics
as
Lara
Gators
been
making
some
changes
to
the
agent
reporting
structure.
There
there's
also
been
a
recent
CLI
release.
C
C
I
know
they've
been
working
with
the
build
packs
team
to
develop
a
contract
for
how
bill
packs
can
supply
sidecar
information
and
have
that
get
wired
into
Kathy
automatically,
and
then
they've
also
been
working
with
the
Diego
team
to
figure
out
how
they
want
to
structure
more
independent
limits
on
the
sidecar
processes
so
like
potentially
being
able
to
provide
a
different
file
system
or
more
independent
partition
to
memory
limits
for
the
process.
That's
running
is
a
sidecar,
some
other
things
have
been
going
on.
C
I
know,
aggregator
has
been
continually
improving
the
some
of
the
agent
reporting
wiring
on
the
library
agents
so
that
they
can
support
syslog
drains
and
even
more
scalable
way,
issues
hey
Josh.
Would
you
mind
meeting
and
also
really
to
scale
the
ireenie
team
has
been
making
some
improvements
to
support
reliability
of
rat
registrations
when
they're
running
at
moderate
levels
of
scale,
they're,
finding
some
inefficiencies
and
had
they
were
reporting
this,
but
I
think
those
are
just
resolved
now.
One
other
thing
potentially
to
watch
out
for
the
bubble.
C
B
C
A
A
So
we
really
have
kind
of
a
set
of
graduating
projects
and
I'll
just
mention
at
this
time
and
then
next
time
you
know
I
guess
just
point
to
the
release
notes
so
autoscaler
you
know
graduated,
so
they
have
widdy's,
be
12.2,
I,
think
it's
just
a
maintenance
maintenance
release,
dough
pack,
stuff
graduated
and
now
it's
the
packs
for
I/o.
So
you
need
to
look
at
that.
A
B
A
Actually.
You
know
they'll
present
that
next
time
then
we
have
the
abacus
project
like
I
mentioned.
That
last
time
is
gonna,
move
to
the
attic
and
then
to
other
projects
that
I
didn't
get
any
updates,
but
they
also
because
the
last
and
monthly
meeting
was
during
a
holiday,
so
we
can
solve
it.
So
I
should
have
stuff,
I
guess
updates
for
next
time.
A
Okay,
let
me
see
if
the
bush
team
sent
me
anything
okay,
so
they
I'm
reading
from
Akash
here
he
said
he
won.
Manifest
report
is
removed,
so
this
is
for
boss,
now
I'll,
add
them
to
the
agenda
as
well,
and
then
he
said
we're
working
to
improve
the
behavior
of
start/stop
recreate
since
we
received
some
feedback
that
they
had
behaved
unexpectedly
and
were
difficult
to
use.
So
I
guess
those
are
two
highlights
for
Bosch,
and
now
this
that's
one.
A
B
B
A
C
Think
that
efforts
are
underway
on
the
build
pack
team
to
transition
to
the
cloud
native,
build
pack
scope
xv-3
with
the
current
plan,
is
for
there
to
be
some
sort
of
shim
to
allow
running
a
v3
build
pack
within
the
current
Clive
foundry
staging
process.
So
that
might
not
take
advantage
of
all
of
the
features
of
v3
build
packs.
But
the
eventual
plan
is
to
rethink
more
generally
how
the
staging
process
works.
C
We
think
Cloud
Foundry
so
that
it
would
be
based
more
on
the
OCI
image
registry
primitives
that
the
cloud
native
Phillip
xv-3
spec
takes
advantage
of
so
I
know.
There's
there's
some
work.
That
pivotal
is
planning
to
open
source
around
that
soon
and
there's
been
some
discussions
amongst
the
project
teams
about
how
that's
going
to
get
integrated
into
college
Henry
great.
B
B
B
Hopefully
this
this
talk
is
topical
and
and
useful,
because
it
goes
back
to
a
blog
post
that
Tim
came
out
with
a
couple
months
ago
and
which
I
missed
entirely
and
I
was
not
at
the
last
cab
call,
but
thank
goodness
the
alt
Horus
people
had
done.
You
know
five
Great
years
of
writing
up
these
capitals
and
because
living
Australia
that's
pretty
much
how
I
lived
them.
B
I'm,
sorry
to
the
you
know,
to
the
recording
team:
I,
don't
typically
watch
sick
that
cool
I
just
read
about
it
and
they
mentioned
a
month
ago.
We
talked
about
sidecars
and
I
was
super
excited
by
that
and
and
in
walking
going
through
the
walkthrough
I
did
all
I
did
Tim's
walkthrough
I
made
that
work,
and
the
first
thing
that
came
out
in
my
mind
is:
why
would
I
push?
B
This
would
no
use
a
bill
pack
and
the
bill
pack
team
agreed
also
that
the
cabbie
team,
I,
think,
agreed
and,
and
so
I
started
investigating
this,
and
you
know
my
my
thoughts
of
experiments
and
and
and
also
the
sir
for
anyone.
That's
never
made
a
bill
pair
just
how
simple
it
is
to
make
like
these.
What
I
call
singles
bill,
packs
and
I
think
it's
super
valuable
to
start
to
look
at
bill
packs
again,
if
you've
never
built
one
or
look
at
the
new
tooling,
especially
with
the
b3
bill
pack.
B
Stuff,
that's
coming
along
I
think
that's
going
to
be
a
greater
demand
for
functionality
be
destructive
into
a
single
purpose.
Bill
pecs,
so
here
we
go,
everything
I
talked
about
is
be
to
build
packs,
but
you
know
we
could
do
this
talk
again
when,
when
we've
got
v3
build
packs
down
the
track,
alright,
so
quickly,
sidecars,
your
app
sits
in
the
container.
B
So
the
premise
is
that
we're
going
to
run
this
other
process
in
the
same
container,
and
since
it
shares
the
file
system,
we
could
our
app
could
connect
to
our
sidecar,
or
vice
versa,
really
I've
said
over
a
socket
or
the
shared
file
system
or
local
port
and
my
example.
He
doesn't
really
match
up
to
my
you
know
to
the
snippet
I've
got
it
below
which
says
that
the
shared
ports
80
and
two,
but
doesn't
really
matter
whatever
it
is.
However,
you
want
the
two
things
to
talk
to
each
other
passively
actively.
B
B
This
has
been
my
sort
of
hope
and
dream
was
that
the
world
would
move
towards.
You
know
proxies
so
that
my
app
would
not
talk
directly
to
Postgres.
That
I
would
talk
to
a
local
proxy
and
my
proxy
could
worry
about
maintaining
that
relationship
with
Postgres
through
through
the
lifecycle
of
Postgres
upgrades,
payloads,
etc
and
yeah
so
I.
This
is
actually
the
demo
we're
going
to
build
later
on,
and
it
wasn't
take
very
long
at
all.
B
There
is
also
perhaps
the
idea
of
running
engine
X
in
the
same,
so
this
is
kind
of
like
a
front-facing
or
this.
The
the
sidecar
in
this
case
might
be
the
thing
that
receives
the
traffic
initially
and
then
for
on
to
the
app
I
did
get
this
working,
bring
up
the
rails
app
and
it
didn't
make
my
app
any
faster.
So
I
wasn't
really
sure
what
to
do
that
yet
I'm
not
sure
whether
I
did
it
wrong
or
perhaps
just
rails.
B
Asset
pipeline
is
fast
enough
and
it
just
doesn't
serve
the
purpose.
But
if
anyone
has
any
wants
to
see
what
I
did,
I
can
show
you,
but
that's
another
example
of
where
Sarkar
and
I
guess,
monitoring
and
other
things
that
arguably
Cloud
Foundry
is
less
useful
site
cards,
because
squad
boundary
does
so
much
stuff.
Already
that
you
know
a
lower
level
system,
like
you
believe,
sidecars
for
all
the
things
we
do
already
in
cloud
foundry,
but
nonetheless
we
have
site
cast
exciting
times,
but
the
thing
Tim
did
was
he
print
the
premise
of
his
thing?
B
Was
he
pushed
the
devisor
developer?
He
was
responsible
for
pushing
some
version
of
the
sidecar
software,
oh,
where
he
got
that
from
as
a
developer
is
kind
of
not
mentioned
like
did
you
have
the
right
version
of
config
server?
Did
he
have
a
patched
version
where,
where
is
that
line
of
responsibility
and
one
of
the
things
I
think
Cloud
Foundry
has
led
the
field
on
in
this
or
platform
space?
B
And
certainly
you
know
all
these
other
things
that
come
along
seem
to
forget
is
this
separation
of
concerns,
and
what
is
this
developers
concern
and
should
the
developer
be
concerned
with
you
know,
figure
out
and
uploading
the
conflict
server
and
I
would
argue
that
it's
the
many
cases
they
should
not.
It
is
not
their
responsibility
and
certainly
further.
You
know
the
front
for
the
examples.
B
We'd
escaped
I
can't
quite
imagine
what
the
example
is
at
the
con
big
server,
where
the
app
developer
would
care
about
the
implementation,
so
we
have
a
model
for
that,
and
that
is
Bill
pack.
So
just
as
another
example,
if
we
were
gonna
go
with
the
xcd
premise,
arguably
there
is
this
other
group
of
people
who
would
care
more
about
psychic
are
self,
then
the
application
developer
and
that's
probably
the
sidecar,
the
HED
service
team,
whoever's
running
that
service,
and
so
it's
more
likely
that
they
would
take
responsibility
for
distributing
that
sidecar.
B
B
That
would
be
super
cool
if
they
could
say
and
now
here's
how
bill
packs
run
psychos,
but
today
we're
just
going
to
distribute
software
in
a
pill
pack,
and
this
has
come
to
what
the
manifest
will
look
like
at
the
end.
We're
gonna
have
our
new
bill
pack
and
we'll
have
explicit
sidecar
and
I'm
gonna,
repeat
myself.
What
sort
of
Eric
was
saying
was
that
hopefully,
if
I
was
to
add
this
sed,
build
pack,
I
wouldn't
perhaps
need
to
explicitly
say
there's
a
sidecar
in
my
application,
manifest
Eric.
Is
that
right?
B
This
is
super
cool
and
but
right
now
you
can
still
go
through
this
process.
You
just
your
application
developers
would
need
to
explicitly
say
that
there
is
a
sidecar
and
mate,
and
this
is
this
premise
of
contact
that
maybe,
instead
of
explicitly
saying
here's
the
command,
you
would
extract
that
down
one
level
to
a
shell
strip,
but
anyway
it's
all
work
in
progress,
but
you
can
get
started
alright.
So
we
are
going
to
go
through
this
little
tutorial.
Walkthrough
now
and
it'll
be
fun.
B
I
tend
to
call
this
a
singles
build
pack,
because
what
we're
gonna
do
is
make
a
build
pack.
That
does
not
contain
lots
of
versions
of
something
like
the
Ruby
build
pack,
lots
of
versions
of
Ruby
and
then
the
application
sort
of
infers
or
suggests
or
whatever,
which
particular
Ruby
it
wants
to
install
the
bill
pack.
B
We're
going
to
build
just
has
one
version
of
in
this
case
at
CD,
and
if
you
really
really
really
need
an
older
version
of
a
TV,
then
you
can
just
explicitly
use
that
old
version
of
the
build
pack
now
later
on.
Maybe
there's
some
break
in
that
relationship
where
users
definitely
need
an
older
version
for
some
reason,
and
then
you
can
make
your
bill
pack
more
complicated
but
getting
started.
B
Now,
let's
make
a
deal
pack
so
now
there
is
what
I'm
not
going
to
show
you
is
the
build
Lib
build.
There
is
a
tool
chain
called
build
pack
packaged
up
and
it
has
like
an
Internet
tool
and
that'll
build
a
scaffold
and
that
can
be
very
helpful.
I'm
gonna
build
up
more
from
scratch.
We're
still
going
to
use
build
pack
packages
to
bundle,
look
together,
but
we're
just
going
to
sort
of
with
the
old
with
with
lower
level
shell
scripts.
So
I'm
gonna
need
a
bins,
folder
the
contract
for
a
supply.
Build
pack.
B
Is
it's
pretty
simple?
It's
it's!
You
just
create
a
supply
script
or
executable,
so
I'm
gonna
make
it
a
shell
script
that
could
be
a
binary
and
we're
gonna
need
a
version
of
what
our
bill
pack
is
and
the
bill
pack
packager
will
medium
or
valve,
and
everything
gets
better
if
it's
actually
executable.
Alright,
let's
make
our
build
pack
that
or
it
exists.
No.
What's
that
that's
not
right!.
B
B
My
hypothesis
in
this
is
that
there
is
another
team
who's
responsible
for
the
sidecar,
and
that
team
is
probably
in
many
organizations
response
to
the
pill
pack.
But
even
if
not
it's
not
developer,
but
we
are
gonna.
You
can
imagine
a
pipeline
like
imagine
a
concourse
pipeline
that
just
watches
the
upstream
thing.
In
this
case,
we'd
have
a
concourse
pipeline.
Watching
the
ad
release.
We
would
get
notified,
get
notified
that
there's
a
new
TV
release.
B
It
would
download
a
specific
thing,
get
the
shower
of
it
and
and
turn
it
into
a
new
version
of
our
build
pack.
We're
going
to
do
this
manually
that
I,
hopefully
you
can
imagine
what
this
would
look
like
as
a
pipeline.
Alright,
so
new
version
came
out
its
3.3
13
I'm,
going
to
go
with
the
again
statement
that
the
version
of
my
build
pack
can
be
in
sync,
with
the
upstream
version
of
the
thing
that
this
is
just
like
a
wrapper.
It's
not
any
fancy
event.
B
It's
just
shipping
that
version
and
anyone
who
wants
to
argue
that
this
is
a
bad
idea
is
very
welcome
to
this
is
where
we're
going
right
now,
so
we're
going
to
say
that
the
version
of
the
bill
pack
equals
the
version
of
the
thing
with
packaging
all
right.
The
next
thing
we
need
is
the
manifest
which
we
don't
know.
What
a
schemer
is.
It's
going
to
be
a
lot
of
fun
to
work
with
so
I'm
just
going
to
copy
one
that
I've
leased
a
starting
point
all
right.
B
So
we
have
a
starting
point
and
you
can
borrow
this
structure
from
every
other
build
pack
that
is
published
by
the
up.
Of
course,
in
most
of
the
bill,
packs
use
the
build
packet
packager
tool.
So,
let's,
let's
rename
this
as
@cd
I'm,
going
to
say
that
the
the
tool
that
the
thing
we're
packaging
is
air,
TV,
I'm
gonna
say
that
buildpack
is
called
the
Italy
proxy
buildpack,
because
that's
really
what
I'm
using
it
for-
and
it
makes
me
feel
better
about
myself
and
the
version
again.
B
B
Let
me
do
this
live
it's
a
little
bit,
embarrassing.
All
right!
We'll
come
back
to
the
shower
the
your
eye.
Now,
because
one
of
the
use
cases
of
a
build
PAC
project
is
people
might
want
to
use
the
git
repo
to
do
it,
in
which
case
they
want
to
download
this
thing.
So
we
will,
and
and
since
we
can
just
get
a
download
URL
from
from
the
place
that
we're
going
to
get
it
from.
B
So
we
will
just
take
that
get
the
URL,
and
we
will
just
paste
that
in
there
turns
out
that,
if
you're
prepared
to
only
work
with
cached
build
packs,
then
you
don't
have
to
push
the
thing
up
to
the
internet
somewhere
public.
You
could
just
have
the
thing
local
on
a
local
file
and
then
create
your
cash
to
build
pack
and
work
with
that.
I.
Don't
know
if
only
I'm
doing
this,
but
it
is
a
thing.
I
just
want
to
mention
it,
but
in
our
case
the
upstream.
B
This
is
where
it
comes
from,
and
but
the
the
supply
thing
that
I'm
gonna
work
on
in
the
short
term
is
going
to
assume
that
it's
a
cached
version
I'm
not
going
to
go
and
fetch
it
from
the
internet.
All
right,
I
have
already
downloaded
this
I.
Don't
you
know
what
no
we
can
download
this?
How
long
could
it
take
honestly
I'm
in
America?
We
have
internet
here.
B
A
lot
less
trusting
of
doing
internet
live
in
Australia,
so
let's
get
the
show
of
that's
there.
It
is
again
your
concourse
pipeline
would
get
all
this
the
week
for
you
we're
good
to
go.
So
what
do
we
do
with
this?
What
we
do
is
we
run
the
build
pack
packager
build
command,
and
it
will
take
that
manifest.
It
will
fetch
all
those
your
roles,
if
I'm
not
already
in
the
cache
and
download
them
again,
and
then
we
will
get
our
cash
to
build
pack
all
right.
So
I
built
this.
B
Set
up
what
the
build
packs
are:
where
are
this
script
is
in
the
bin,
folder,
so
we'll
say
the
bill
pack
directory
is
one
down
and
let's
have
a
little,
have
ourselves
a
look-see
at.
What's
in
that
folder
during
staging
that
looks
pretty
good
as
a
bit
of
a
no
op
bill
pack,
and
so
we
are
going
to
make
that
again
and
then
we
will
create
it
and
upload
it
so
see
if
create
bill
pack.
I
apologize
for
cheating,
but
this
is
the
the
admin
command
for
creating
a
new
bill
pack.
B
B
B
Which
again
I
apologize
to
my
anal
retentiveness,
even
though
we're
never
gonna
actually
see
this
I
feel
like
it
should
say
hello
world.
Now,
when
we
get
back
to
sidecars,
it
is
the
newbie
three
commands
that
we're
going
to
need
so
we'll
come
back
to
those
in
a
second
for
the
short
term.
Let's
just
use
the
simple
ones
just
to
get
moving.
B
Okey-Dokey,
so
it's
now
moved
on
to
the
stereo
build
pack
staging,
but
we
can
see
here
my
build
pack
in
action
and
the
showing
of
the
build
pack
contents
and,
as
we
said,
as
we
sort
of
showed
that
all
it's
done
is
unpacked,
that
zip
file
into
some
folder,
so
that
was
build
Pachter
and
then
here's
our
dependencies,
someone
one
day,
might
explain
to
me
what
this
number
is.
But
here
is
my
upstream
file
that
we
could
you
know
now
use
we
don't
yet
have
this
pretty
line.
B
We
should
get
this
pretty
line
and
put
it
in
so
that
our
bill
pack
looks
like
everyone
else's
built
back.
So
let
us
now
echo
it
CG.
No,
it's!
Never!
It's
never
too
early
to
make
you
build
pack
look
cool,
and
now
we
want
some
version
number
turns
out
our
bill
pack
has
our
version
file
in
it.
So
we
know
where
that
version
is
so,
let's
get
that
out.
B
B
What
I
do
need
is
perhaps
to
unpack
this
and
have
a
look
see
inside.
So
let's
tar,
fixit's
there'd
build
pack
the
dependencies
and
again
not
sure
what
that's
for,
but
I
do
happen
to
know
what
this
file
looks
like
now.
There
you
know
at
this
point
other
people
you
have
showing
us
that
take
that
step
back.
We
do
have
the
manifest.
Also
so
perhaps
more
correctly,
I
should
look
inside
that
manifest
in
real
time.
B
You
know
during
staging
pull
out
this
file
and
you
know,
etc,
etc,
etc
and
get
the
white
one,
but
the
fear
linux,
fs3
filesystem,
doesn't
have
tools,
processing
mammals
best
as
I
can
tell
so
that's
just
one
step
too
far,
and
since
we're
our
build
pack
only
does
one
thing
and
I
know
everything
about
it.
We're
just
going
to
go
straight
it
to
oh
I've
got
the
wrong
file.
Let's
go!
B
That's
not
gonna
work
very
well,
but
whoever
didn't
tell
me
that
I
downloaded
the
wrong
file
awful
human
beings,
but
we
need
that
one
that
wasn't
gonna
work
at
all
arm
64
likes.
So,
let's,
let's,
let's,
let's,
let's
go
back
a
step,
so
I
need
to
fix
that
I
need
to
download
the
correct
thing.
I
wouldn't
have
got
us
very
far.
Unless
we're
gonna
deploy
this
to
a
Raspberry
Pi.
B
B
There
we
got
there,
AMD
will
take
that
shot
and
we
will
D
again
so
I
should
pass
that
yen
will
file
and
get
the
value
out,
etc.
But
since
I
know
everything
about
what
I'm
downloading
I
know,
what
its
name
looks
like,
so
we're
just
going
to
yeah
pop
it
in
there.
We
should
unpack
this
somewhere,
rather
than
just
where
we
are
right
now.
So,
let's,
let's
make
a
little
tempter.
B
And
so
now
we're
inside
that,
let's
go
to
pop
that
in
brackets
and
yeah.
So,
let's
and
let's
see
what
we
get
again,
this
is
just
my
process
see
what
would
see
what
we
unpack
all
right.
Let's
go
through
this
sequence
again,
so
we're
going
to
create
the
build
pack
and
then
we're
going
to
you
know
what
there
is
an
update
command
but
I,
don't
like
I,
don't
like
it,
so
I
tend
to
delete
and
create
and
then
we're
going
to
push
so
we're
gonna
run
those
commands
over
and
over
again
during
iteration.
B
C
B
Look
at
that,
what
do
pack
looks
great
already
with
you
know,
doesn't
look
good
if
it
doesn't
have
to
look
at
that.
It
looks
like
a
build
pack,
all
the
sudden,
okay,
so
in
our
unpacked
folder,
which
was
dot
we
get
this
folder
and
inside
that
folder
is
our
to
see
lies,
and
this
is
what
we
want
really
really
don't
need
the
rest
of
the
documentation.
Everything.
What
we
want
is
to
unpack
these
into
the
finals
droplet,
and
you
want
them
to
be
in
the
path,
because
that's
even
better,
so
we
can
just
use
them.
B
B
B
Let's
just
plot
these.
In
typically
you
just
do
this
always,
and
even
if
you
don't
use
them
all,
you
males
will
document
what
the
inputs
are,
and
so
the
build
directory
is
that
app
that
you're
working
on
so
we
could
interfere
with
the
app
and
change
it
and
change
files,
but
our
build
pack
is
independent
of
the
app
and
we're
not
going
to
touch
the
folder.
There's
the
cache
there
for
caching
things,
and
oh
these
two.
This
is
the
important
ones
we
want
these
ones.
B
So
if
we
put
things
into
the
dependencies
directory,
it
will
allow
us
to.
You
know
this
is
our
built
out
there.
There
are
multiple
like
so
as
the
staging
happens,
all
the
build
packs
are
there,
but
we
only
want
to
interfere
with
the
build
pack
directory
for
the
dependency
directory
for
our
build
pack,
not
sure
what
bad
things
happen.
B
B
B
So
if
we
go
into
Xero,
we
see
there's
nothing
in
there.
That's
a
shame,
but
this
is
where
we
will
be
putting
our
ETV,
so
we
will
be
creating
a
bin,
folder
and
inside
that
will
be.
You
know,
creating
the
ETD
binary,
obviously
whoo
and
just
be
praying
and
people
don't,
but
at
all,
but
that's
what
we're
about
to
do.
So
we
don't
know
what
you
know
at
the
time
that
we're
writing
this
supply
thing.
B
B
So
we
will
copy
that
into
bin
now
that
the
novelty
here
is
that
if
you're
Bill
pack
creates
a
bin
folder,
it
will
be
added
into
the
path
automatically
after
staging
or
when
the
shell.
So
that's
that's
super
nice,
but
just
right
now
it's
not
so.
Let's
drink
staging
it
I,
don't
believe
it
is.
So,
let's
add
it
to
the
path
where
our
own
entertainment
and
let
us
check
that
it's
you
know
working
then
we'll
delete
this
later.
We
don't
need
that
anymore
and
I.
B
B
A
B
Mean
this
process
is
very
similar
in
the
process
of
creme
Bosch
releases
and
Bosch
packages
or
docker
files,
and
you
just
keep
you
live
in
a
perpetual
state
of
nothing
works
and
then
also
that
does
work
and
instead
of
embracing
enjoying
that
process
of
things
working,
you
move
on
to
other
things
that
aren't
working.
That's
our
profession!
Really!
That's!
Why
I
like
to
stop
when
something
works,
because
I
like
to
embrace
that
it's
right.
B
Cool
all
right
that
will
work
a
treat
now:
okay,
while
that's
building
and
demonstrating
with
a
TV,
is
now
installed.
We
can
take
a
step
towards
the
sidecar
part
of
this.
Talk.
You've
now
learned
how
to
build
a
bill:
packets,
a
very
simple
bill
pack
that
just
always
installs
the
latest
of
whatever
it
is
that
it's
got
into
it,
and
there
koroliov,
though,
is
that
this
supply
script
assumes
that
you're
using
cash
to
build
packs.
B
Then,
if
you
wanted
to
support
uncashed
or
the
using
it
from
github
from
get,
then
you
would
also
need
to
support.
You
know
the
feature
where
this
is
where
that
isn't
available.
So
if
a
none
cash
buildpack
would
have
nothing
under
the
dependencies
folder
or
no
dependencies
folder,
and
you
would
need
to
go
to
the
manifest
pull
out
that
URL
and
download
it
either
through.
Whatever
you
know
at
all,
you
want
to
use
the
tool
that
I've
started
using
is
from
Stephen
Levine's
YJ
tool.
I
find
that
quite
handy
it
it's
kind
of
cool
it.
B
B
B
B
Back
to
this,
so
what
we
know
that
I
do
want
to
prove
a
point
is
that
during
the
runtime
of
our
container,
because
we
put
the
because
we
created
a
bin
folder,
it
is
automatically
added
to
the
path.
So
this
is
where
we
put
it
CD
and
therefore
a
TV
is
available
in
the
path
inside
a
container.
Therefore,
I
don't
need
to
put
any
path
here
and
we're
good
to
go.
B
This
is
the
command
that
you
would
read
in
the
documentation
about
how
to
run
a
CD
proxy,
and
this
is
where
you
would
put
a
list
of
of
hosts
to
start
with
I'm
on
CF
dev
and
see
if
there
has
this
cool
feature
where
this
domain
DNS
entry
references,
my
local
machine
or
the
host
machine,
and
so
this
will
point
to
the
sed
server
that
I
have
on
on
my
local
machine.
So
if
I
was
to
say,
set
local
da
clinic,
that's
it
what's,
it
called
put.
B
We
can
in
a
minute,
see
that
I
can
get
that
from
my
container
and
we
want
to
listen
and
I
explicitly
just
on
the
local
host
on
the
same
port
that
that
client
might
normally.
And
what
this
means,
though,
is
that
my
client
app,
which
is
just
static-
it's
not
going
to
talk
to
a
TV
at
all.
Only
needs
to
talk
to
this
doesn't
need
to
be
configured,
no
need
for
it
to
know
about
certificates,
etc,
etc.
B
The
build
pack,
because
you
iterated
this
build
pack
with
setup
certificates,
would
do
all
the
things
to
make
it
have
a
better
relationship.
You
would
not
hard
code
this
in
here.
You
would
have
some
sort
of
you
know:
abstract
command.
Like
start
Etsy
do
SH
and
we
would
create
the
shell
script
and
we
would
look
up
these
end
points
from
be
kept
services
and
build
this
this
command,
but
all
that
is
out
of
scope
for
the
four
minutes.
We
have
remaining
all
right.
B
B
B
All
right,
it's
exciting!
It's
only
exciting
if
you
can
start
to
imagine
what
what
so
cars
might
be
good
for,
but
you're
still
watching.
So
now
you
might
just
to
be
clear.
You
might
have
seen
me
delete
that
from
here
and
yet
they're
still
being
printed
out.
Of
course,
I
have
not
yet
created
and
uploaded
to
the
new
build
pack.
Therefore,
I'm
getting
the
most
recent
build
back.
C
B
You
hooray
look
at
us,
so
this
is
what
a
sidecar
looks
like
in
your
logs.
We
get
this
set
of
web
/
0
we
get
web.
You
know
what
I
kind
of
think
that
probably
should
still
be
web
/
0
to
sort
of
point
to
the.
But
anyway
it's
got
the
0,
the
answer,
whatever
I
guess
it's
web
and
zero
represents
the
container
and
we
looked
at
before,
but
there
is
our
psycho.
B
The
psych
I
has
a
name
which
came
from
the
manifest
that
was
that
name
they're
put
into
couples
and
and
anything
that
it
outputs
to
stand
out
will
go
they're,
not
a
hundred
percent
sure
why
it's
it's
they're,
not
just
moving
on
I'm,
sorry,
just
as
sit
so
for
a
while,
eventually
works,
which
is
a
bit
not
great
for
demos.
It's
a
bit
boring
I
feel
like
I
have
to
keep
talking,
but
before
the
final
finale,
where
I
demonstrate
that
it
works.
Does
anyone
have
questions.
A
B
B
B
Whatever
all
right
that
refuses
to
work
and
I,
don't
know
why
so
I
apologize
for
that
the
demonstrations
are,
let's,
let's,
let's
wrap
up
so
I
I.
You
know
what
if
I
could
think
of
lots.
I
would
have
started
I.
The
first
one
I
tried
was
console.
I
thought
that
would
have
been
cool,
but
it
turns
out.
The
console
is
sort
of
has
multiple,
really
it's
sort
of
a
bi-directional
connection,
I
think
and,
and
it
was
having
trouble.
B
B
Maybe
you
listen,
but
it's
not
here
so
Rebekah,
suggesting
in
the
cage
can't
read
screen,
there's
something
about
listening,
but
the
part
that's
not
working
is.
This
is
not
my
bit
it's
the
static
file
bill
pack,
nginx
listening
on
on
on
8080,
so
it's
it's
not
even
month.
So
my
fault,
it's
not
my
fault,
our
blind,
see
if
they've.
Typically,
it's
always
see.
If
deadfall,
you
know
what
we
can
just
start
pushing
again
pushing
again
might
just
fix
it.
You
know,
stop
and
start
again.
C
So
the
use
cases
might
be
something
quite
grinding
APM,
alongside
with
application.
The
question
is:
if,
if
like
APM
is
ironic
or
something
else
is
running,
we
might
want
need
to
modify
the
main
build
park.
If
there
is
such
a
thing
release,
so
what
what
it
is
is
is
emitting
as
the
main
command
to
learn
so,
in
other
words,
how
your
parks
can
communicate
with
each
other
to
modify
parameters
of
each
other
like,
for
example,
if
I
have
a
job
I
built,
Parkinson,
APM
I.
Might
what
wanted
to
inject
something
in
right?.
B
If,
if
the
app,
if
a
certain
new
pack
is
also
available,
then
add
this
flag
to
this
document,
you
mean
that
sort
of
thing
yeah,
and
that
is
definitely
I-
think
they're
they're
they're
stumbling
through
that
with
no
stomach
northwood
in
the
b3,
where
they're
starting
to
tease
these
things
out
right.
There
is
a
PHP
build
prac,
but
that's
not
the
one
that
you
can't
just
use
that
and
assume
your
app
is
going
to
run
on
PHP.
B
So
your
your
staging
can
create
profile,
shell
scripts,
that
will
be
loaded
into
memory
and
they
are
loaded
up
before
every
process,
and
so
you
could
be
putting
things
into
environment
variables
about
AI
exist
or
you
could
be
creating
files
dynamically
based
on.
What's
in
Barbie
cat
services
in
other
environment
variables,
and
then
the
start
scripts
would
start,
and
they
could
have
collected
this.
This
sort
of
information.
But
you
could
also
just
look
at
the
file
system
and
say:
does
this
bill
pack
exist
which.
C
C
B
Only
the
last
one
has
it's.
Finalized
script
run
now
that
this
contract
may
change,
and
this
you
know
when,
when
they'd
the
bill
pack
and
cap
Eugene
were
together
on
our
supply,
bill
pack
might
be
able
to
inject
itself
its
owns
the
patch.
It
will
have
a
support.
Finalized
pack
that'll
be
the
contract
that
a
supply
script,
a
supply
bill
back,
might
be
able
to
have
a
finalized.
B
Maybe
it's
it's
a
called
sidecar.
Something
like
that.
There
might
be
some
contract
that
if
this
this
endpoint
exists,
then
that
is
where
you'll
start
your
sidecar,
maybe
I'm.
Just
you
know,
I've
no
idea
until
Eric
mentioned
that
I
wasn't
aware
of
it
any
progress,
but
you
know,
maybe
you
put
that
there
and
that's
how
the
psycho
gets
prepared.
B
Yeah
I,
sorry
all
right
how
they
affect
each
other.
Let's
chat
afterwards,
because
I
feel
like
I,
might
be
going
away
the
place.
Let's
have
a
look
inside
a
working
thing,
and
so
we
can
see
that
there
is
nginx
and
there
is
our
sidecar.
So
that's
exciting.
It
also
means
I
do
happen
to
have
the
there
and
remember
I
put
that
there.
So
if
I
now
go
into
my
container
and
I
get
local
look
at
this,
it
works,
and
that
is
pretty
exciting.
Obviously,
there's
more
to
be
done,
you
would
have
to
look
up.
B
B
Put
that
in
there,
but
I
now
need
to
get
this.
This
set
of
host
names
from
somewhere
right.
So
it's
now
I
need
to
sort
of
you
know
echo,
be
capsule
services,
etc,
etc,
etc.
They
cube
magic
right,
post
e,
well,
something
like
that
to
get
it
out
and
that's
sort
of
process
of
the
defect
in
a
way
and
setting
up
certificates,
all
the
other
parts
of
other
authentication
or
security,
etc.
B
But
that
is
the
gist
of
it,
and
it
is
really
easy
and
I've
done
it
with
shell,
just
as
a
sort
of
a
call
out.
There
is
the
where
the
built
pact,
where
that's
that
command
came
from
using,
is
this
library
here,
and
it
has
a
bunch
of
tools
in
it
for
writing
all
of
your
bill
pack
in
go.
If
that
is
how
you'd
like
to
do
it,
which
is
how
the
longer
the
court
in
your
pets
have
been
done
so
I'm
five
minutes
over
I
just
met.
B
B
B
B
C
C
B
If
you
wanna,
if
you
have
an
example
like
we
can
sort
of
parent-
and
perhaps
I
can
point
to
how
you
might
solve
that
problem,
but
essentially
the
staging
the
build
patter,
your
supply
bill
pack
could
put
some
files
on
the
file
system.
Lets
them
say:
hey
I'm
there
I
could
create
a
profile,
deep
script
that
gets
loaded
into
memory.
They
could
add
environment
variables
to
say,
hey,
I'm
there
and
here's.
B
B
Of
course,
I
spelt
that
so
close
to
almost
being
a
thing:
imagemagick
free,
tds,
wordpress,
CLI,
I'd
started.
What
is
this?
It's
interesting
to
start
to
use
these
supply
bill
packs
to
make
it
easier
to
bring
non
Cloud
Foundry
type
things
into.
This
is
a
fun
one,
the
dot
profile.
Everyone
can
upload
a
profile
except
Java
people
easily.
So
this
bill
pack
means
that
you
can
and
look
how
simple
it
is.
It's
literally
just
you
know
that
so
bill
packs
are
fun
and
I.