►
From YouTube: Nexus Repository OSS Walkthrough: UI Overview
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
Hello
and
welcome
back
to
my
demo
of
the
Nexus
repository
manager
in
the
last
video
I
installed
Nexus
and
got
it
up
and
running
locally
and,
as
we
could
see
here,
it's
still
running
in
my
localhost
and
in
this
video.
What
I
would
like
to
do
is
an
overview
of
the
application
just
to
get
a
sense
of
what's
included
and
then
in
the
next
video
we'll
actually
walk
through
a
use
case
and
a
demo
of
the
product
itself.
A
Ok,
so,
let's
start
with
the
top
map
bar.
If
we
start
on
the
top
right,
I
could
say
this
is
where
I
would
sign
out
this
where
it
says
admin
here.
This
is
actually
my
username.
If
I
click
this,
it's
basically
I
have
the
option
to
adjust.
My
name
and
my
email
here
is
also
where
I
could
set
my
you
get
API
key.
So,
if
you're
using
Nexus
to
access
NuGet
packages,
you
could
also
authenticate
with
this
API
key
here.
A
This
question
mark
has
really
helpful
links
to
their
documentation.
Their
knowledge
base
the
community
as
well
as
an
issue
tracker,
and
then
here
we
see
this
is
sort
of
a
system
status
check.
So
you
can
see.
Is
the
system
up
and
running?
Are
there
any
issues?
And
then,
if
you
setup
any
policies,
are
there
any
violations
of
those
policies?
A
A
Ok,
that's
kind
of
an
overview
of
sort
of
how
to
navigate.
There
are
two
really
important
sections
of
the
application.
The
first
one
is
this
server
administration
and
configuration.
This
is
where
we're
going
to
do
things
like
configure,
object,
storage,
expiration
policies,
connect
to
different
repositories
and
set
up
different
searchable
search
for
it.
I
would
search
queries
that
you
can
be
used
for
other
people
within
the
application
and
then
on
the
Browse
section.
A
A
So
in
repository,
let's
dive
into
some
of
these
or
sorry
in
the
this
admin
section,
let's
dive
into
these
five
different
configurations
so
for
blob
stores.
This
is
really.
This
is
how
storage
is
handled
for
Nexus.
For
me,
I'm
running
this
locally,
so
I'm
fine
using
their
default
option,
which
basically
is
using
my
hard
drive
currently
using
less
than
10
Meg's
and
I,
could
see
that
I
can
also
enable
quotas
that
will
limit
how
much
storage
is
actually
used.
A
A
See
so
updating
the
configuration
will
make
a
temporary
I'm
temporarily
unavailable
so
I'm
going
to
avoid
setting
any
changes
to
the
flop
store
here,
but
this
is
where
you
would
do
that.
In
addition,
you
could
also
create
one
and
you
have
the
option
of
plus
two
for
it
to
be
a
file
or
you
could
connect
as
three
here
as
well,
and
then
you
just
put
it
in
the
path
of
the
store.
You're
connected.
A
A
So
the
criteria
here
is
to
clean
up
any
images
that
were
removed,
the
four
components
that
are
more
than
30
days
old
and
match
the
name
dev.
This
is
a
really
nifty
feature
you
can
say
to
publish
before
or
last
downloading
before,
and
you
can
also
use
regular
expression
to
match
up
the
component
names.
You
also
have
the
option
to
preview
results
and
then,
of
course,
save
it
so
I'm
going
to
discard
my
changes
there,
you
can
create
a
new
cleanup
policy
and
it's
basically
the
same
thing
that
we
just
went
through.
A
A
We
see
a
few
different,
maybe
repositories,
one
called
central
proxy
public
releases
and
snapshots,
and
then
for
types
we
see
proxy
group
and
hosted
so
what
Nexus
does
is
the
a
hosted
repository
is
one
that's
hosted
locally
as
part
of
your
Nexus
application.
So
this
would
be
a
private
repository
that
you
and
your
team
have
access
to.
They
also
give
you
the
option
to
proxy
other
repositories.
A
So
I
could
see
here
that
this
group
includes
Maybin
releases,
Maybin,
snapshots
and
maven
central.
What
this
means
is
that,
when
I
access,
when
I
try
and
pull
a
package
from
Nexus,
it
will
first
look
for
the
item
in
maven
releases.
If
it's
not
there,
then
it
will
try
and
find
it
snapshots
and
then,
if
it's
not
there.
Finally
it'll
look
in
the
public
maven
repository
maven
central
and
now
you
can
set
an
arbitrary
number
of
depositories
of
this
and
maintain
the
logic.
A
Ok,
let's
go
back
to
the
repositories
you
can
also
when
you're
here
you
could
see
you
could
filter
on
format
status.
You
can
very
quickly
copy
the
URL.
So
if
you're
trying
to
just
copy
that
you
can
easily
share
it
and
then
they
have
some
security
features
in
here
as
well.
So
you
can
analyze
your
repositories
and
then
you
can
see
if
there
are
any
violations.
If
you
have
Nexus
IQ,
Nexus
IQ,
it
allows
you
to
set
up
rules
and
policies
for
preventing
any
malicious
software
from
making
its
way
into
your
into
your
software.
A
Okay,
then
we
have
routing
rules,
so
routing
rules
are
ways
of
setting
up
access
and
permissions
to
different
repositories.
So
you
can
create
a
routing
rule
based
on
really
any
criteria
and
set
up
tests.
It's
a
pretty
cool
way
of
setting
up
security
protocols,
and
then
they
have
something
here
called
content
selectors,
and
what
this
is
is
really
is
way
of
searching
for
specific
components
within
Nexus
Nexus
gives
you
the
option
of
using
something
that
they
call
C
SEL,
which
is
their
version.
A
I,
don't
want
to
call
it
sequel,
but
it's
their
way
of
searching
for
packages
within
Nexus,
and
then
they
have
documentation
for
what
this
looks
like,
but
they
give
us
an
example
here.
So
in
this
example,
I
could
search
for
all
maven
to
content
along
a
path
that
starts
with
a
given
domain
name
given
URL,
so
here,
I've
put
format
equals
equals
if
I
wanted
to
do
matches
instead
of
equals,
I
could
use
something
like
equals
tilde
and
then
that
would
search
for
just
matches.
So
this
is
pretty
cool.
A
A
Okay
and
then
that's
that's
it
for
the
Edmonton
configuration
section.
The
final
piece
that
I
would
like
to
show
is
the
Browse
section.
So
this
is
where
you
would
actually
look
for
any
of
the
packages
on
your
system.
So,
for
instance,
I
could
take
a
look
at
Nathan
public
and
in
this
case
I
haven't,
haven't
gone
through
and
set
everything
up
yet
so
no
components
are
here,
but
this
is
when
I
actually
do
do.
My
search
I
can
find
any
of
my
components
here
and
it'll
have
details
about
them.
A
So
for
that
piece
stay
tuned
for
the
next
portion
of
the
video
in
which
we
will
go
through
the
remainder
of
the
application.
We
will
set
up
an
a
remote
NPM
cross,
google
proxy
at
public
NPM
registry,
then
we'll
set
up
a
private,
hosted
NPM
registry
and
then
we'll
group
them
together
and
define
an
ordered
logic
that
makes
sense
for
our
use
case,
so
stay
tuned
for
that.
Next,
video
and
I
look
forward
to
sharing.