►
From YouTube: Nexus Repository OSS Walkthrough: Closing remarks
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
We
proxied
requests
from
the
public
repository,
we
publish
private
packages
and
we
saw
how
the
group
repository
is
really
useful
for
handling
the
ordering
and
definition
in
which
packages
are
pulled.
I
want
to
just
give
a
couple
of
other
quick
notes
of
things
that
I
found
useful
or
worth
noting.
I
thought
the
install
process
for
Nexus
was
really
easy.
A
For
gitlab
in
in
12:9,
we
launched
a
feature
that
will
automatically
pull
packages
that
are
not
found
in
your
github
repository.
It
will
pull
them
from
the
public
registry.
I'd
really
like
to
add
in
the
coming
months,
the
ability
to
set
up
an
arbitrary
amount
of
external
repositories
and
provide
a
single
URL
endpoint,
like
what
Nexus
is
doing
here
for
installing
packages,
I
thought
the
documentation
was:
okay,
I
had
a
there,
they
have
a
lot
of
resources.
I
found
a
lot
of
duplicate
content.
A
They
have
some,
in
some
cases,
they're
pointing
you
here
to
setting
up
the
repositories
from
NPM,
but
and
then
in
other
cases,
they're
pointing
it
to
a
node
page
and
then
there's
also
these
learn
pages.
So
I
didn't
I
had
a
hard
time
finding
a
single
source
of
true
for
what
I
was
supposed
to
follow
for
documentation,
even
though
all
of
it
was
easy
to
follow
and
relatively
close
I
thought,
the
authentication
was
relatively
straightforward.
A
I
didn't
have
any
problems
with
that,
although
in
the
documentation
I
had
to
jump
ahead
to
find
out
exactly
how
to
do
that,
I
was
a
little
confused
about
the
switching
back
and
forth
between
the
repositories
page
and
the
Browse
page
I
found
myself
often
when
I
wanted
to
try
and
find
a
package.
I
would
click
into
the
repository
and
then
instead
I
had
to
go
back
to
the
Browse
I
guess
I
am
not
using
it
enough
to
really
take
advantage
of
the
content.
Selectors
I
feel
like
if
you
have
many
teams
and
many
developers.
A
This
is
probably
a
really
useful
tool.
I
didn't
find
this
very
intuitive
I
hope
that
forget
lab
that
we
can
improve
on
search
and
discovery.
I
thought
cleanup
policies
was
a
really
useful
and
I
thought
that
the
name
clean
up
policies
I
like
that
better
than
expiration
policies,
because
it
does
speak
to
both
retaining
and
expiring
packages
or
images.
A
This
a
minor,
minor
nitpick
now
that
were
this
deep
I,
didn't
appreciate
that
I
couldn't
really
customize
my
user
account
too
much
and
would
want
to
add
an
avatar
or
maybe
add
in
some
extra
information
here,
but
overall
I
thought
this
was
a
really
awesome
application.
I
think
I
learned
a
lot
doing
it
and
I
hope
that
this
was
useful
for
you
watching
along.
Thank
you
very
much
and
I'll
talk
to
it.