►
From YouTube: Nexus Repository OSS Walkthrough: Private repositories
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
So
we
have
this
NPM
private
repository
that
was
set
up,
and
this
was
really
easy
to
do.
I
just
added.
They
asked
me
for
a
name
as
well
as
for,
and
then
they
provided
this
URL
endpoint
I
didn't
set
any
cleanup
policies
or
change
any
of
the
blobstore
okay.
So
let's
follow
along
in
the
documentation
and
the
first
step
will
be
to
let
attempt
to
authenticate
using
realm
and
login.
So,
let's
try
copying
this
command.
A
A
A
Okay,
the
so
we
authenticated
using
Roman
log
and
we'll
see
if
that
works
you.
They
also
give
you
the
opportunity
to
authenticate
using
basic
off.
So
what
you
would
do
is
you
would
encode
your
Nexus
repository,
username
and
password
in
base64,
and
then
you
plug
in
and
use
those
credentials,
let's
try
it
with
the
basic
off
and
see
if
it
works.
So
now
we
are
ready
to
publish
NPM
packages
and
there
are
two
options
here.
A
So
when
you're
building
the
package,
which
essentially
is
a
package.json
file
with
a
recipe
in
it,
you
can
either
explicitly
state
the
registry
in
which
you
want
to
publish
it.
You
using
the
command
line,
so
I
could
say.
Npm
published
and
I
could
specifically
point
to
my
NPM,
private
registry
or
I
can
add
a
publish
config
to
my
package.json
file,
so
I've
created
a
package.json
file.
I
have
a
package
called
beans.
A
A
Boom
done
so
one
more
thing
I'd
like
to
check,
is
when
we're
browsing
I'd
like
to
know
that
the
NPM
all
this
is
my
grouped
repository
also
has
now
has
the
beans
package,
and
it
does
I
could
also
see
it
in
my
all
package
in
my
own
repository
all
right.
Well
so
far,
then
what
we've
done
is
we've.
Given
we've
installed
Nexus,
we
have
given
an
overview
of
the
user
interface.
We've
set
up
a
proxy
repository
to
pull
packages
from
the
public
NPM
registry.