►
From YouTube: Package: Dependency Proxy speedrun
Description
Quick speedrun of using the dependency proxy to download the latest golang image and cache it for future pulls
A
Well,
I'm
Tim
I'm,
the
product
manager
here
for
the
packaged
stage,
and
today
I
just
wanted
to
record
a
quick
demo
of
or
a
quick
speedrun
of
using
the
dependency
proxy.
The
dependency
proxy
is
a
feature
that
requires
Puma,
which
is
still
in
experimental
mode,
but
it
will
allow
you
to
proxy
and
cache
upstream
images
from
docker
hub,
so
it's
available
at
the
group
level,
so
I'm
going
to
open
up
my
get
lab
out.
A
I
have
a
group
here
called
feature
testing
and
if
I
navigate
to
packages
and
dependency
proxy
I
could
see
user
interface
here,
which
says
I
have
the
ability
to
enable
or
disable
it
and
I
could
also
see
how
many
blobs
of
images
are
being
cached.
It's
important
to
note
that
the
manifests
for
the
images
are
not
cached,
but
these
are
typically
very
small
text
files
anyway.
A
So
there
are
not
so
many
there's
not
so
much
of
a
performance
enhancement
of
being
able
to
cache
these
okay,
so
I
want
to
use
it
and
scroll
down
to
the
documentation
and
it
does
require
get
blab
1111.
Ok,
so
I'm
going
to
manually
pull
the
image
and
it
says
here:
I
just
have
to
do
doc
or
pull
and
then
I
put
in
my
via
the
my
host
name,
the
group
name
and
then
dependency
proxy
and
containers
okay.
So
let's
open
up
a
terminal.
A
A
A
A
So
all
of
this
time
that
it's
downloading
the
layers,
typically,
what
would
happen
is
if
you're
applying
this
from
C
I
would
download
these
the
image
each
time
for
each
job.
But
now,
with
the
dependency
proxy,
it
will
download
one
time
and
then
it
will
be
available
in
cash
for
the
next
time
you
use
for
each
job,
so
this
will
be
it'll,
be
much
faster
to
to
download
and
to
to
use
images,
at
least
from
docker
hub
for
your
project.
A
A
A
It's
gonna
tell
me
the
image
is
already
up
to
date
and
exists,
so
I
just
saved
all
that
time
in
downloading
the
image.
Okay,
that's
how
the
dependency
proxy
works,
and
you
could
view
the
documentation
on
get
lab
of
course,
and
we
also
have
this
epic
number
two
to
a
2
and
this
details.
What's
upcoming
for
the
dependency
proxy.
So
next
on
our
list
is
we
want
to
add
authentication
for
so
we
could
support
private
projects.
A
We
are
potentially
going
to
update
the
dependency
proxy
to
use
workhorse
for
the
download
logic
instead
of
the
web
servers
and
instead
of
relying
on
Puma,
which
is
currently
only
in
experimental
phase
and
then
we'll
add
the
ability
to
delete
items
and
purge
them
and
then
we'll
start
to
add
in
support
for
different
package
managers
like
NPM
and
maven,
and
also
new
get
alright.
Thank
you
very
much
and
if
you
have
any
questions,
feel
free
to
reach
out
to
me
at
T
busy
advocate
lab
comm.