►
From YouTube: GitLab Composer Repository Demo for Commit
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
I
am
a
worker
city
angle,
a
technical
advantage
program
manager
at
gitlab
in
this
demo
I'll
be
showing
you
how
you
can
publish
your
gitlab
project
into
the
composer
repository
registry
that
was
recently
introduced
in
gitlab
13.2,
and
also
how
you
can
embed
use
those
as
dependencies
in
your
subsequent
project.
Yeah
I'll,
be
showing
you
two
things:
basically,
how
to
publish
your
project
into
the
registry
and
how
you
can
use
them.
So
I
have
two
projects
already
created
for
the
purpose
of
this
demo.
A
The
first
one
is
a
composer
package
that
I've
already
created
and
the
second
project
will
consume
the
package.
I've
created
to
show
you
how
it
works
so
for
the
purpose
of
this
demo
I'll
be
using
the
they
said
so
api
to
get
a
quote
of
the
day.
It's
basically
returns
a
code
and
the
author
of
the
code.
So
now
let
me
show
you
a
walkthrough
of
my
composer
package
project
now.
A
First,
the
most
important
aspect
of
any
pro
composer
project
is
the
composer.json
file.
This
is
where
you
specify
everything
about
the
package:
what
dependencies
has
the
authors,
the
library,
the
line
sentences
and
so
on
so
for
this
particular
package,
I'm
requiring
gozole,
so
I
can
make
requests
over
the
internet
over
the
network
and
I've
also
specified
an
auto
load
here
that
anytime,
the
namespace
quotes
is
called.
A
It
should
look
in
the
source
folder
now
and
I've
specified
the
name
of
my
package.
This
is
also
important
to
abubakar.
Slash
quotes,
that's
my
name.
Slash
quotes
now
for
a
quick
walkthrough
of
how
basically,
what
how
the
package
is
built
is,
I
simply
have
a
single
class
called
quotes,
and
within
this
class
we
can
call
the
kod
method,
which
is
the
question
of
the
day,
a
quote
of
the
day
method
and
it
returns
to
us.
A
After
making
an
api
call
to
the
codes
api,
it
returns
to
us
a
code
and
the
author
of
the
code.
That's
basically
what
the
package
does
now.
Also,
once
you've
created
your
composer.json
file,
everything
is
acceptable
to
you.
The
next
thing
is
to
create
a
gitlab
shared.yamu
file.
Now
there
are
two
parts
to
my
ci
file
here.
The
first
one
is
my
test
stage.
It's
basically
for
me
to
run,
do
composer
updates
to
get
all
the
necessary
packages
that
I
need
all
the
necessary
dependencies
for
my
packages
and
also
see
if
everything
is
working.
A
A
Now
you
don't
necessarily
need
to
wrap
your
hand
around
how
this
was
constructed.
Gitlab
already
provides
it
as
part
of
the
gitlab
ci
templates,
for
example.
If
I
cut
everything
here-
and
I
come
to
the
list
of
templates
that
will
have
listed
here-
and
I
enter
composer-
is
going
to
just
display
for
me
a
pretty
a
predefined
template
of
how
you
can
publish
your
composer
package
to
the
inbuilt
registry.
You
don't
necessarily
need
to
edit
anything
here.
It
already
uses
all
the
ci
variables
that
is
required
to
publish
your
package
now.
A
Basically,
what
it
does
here
is.
It
uses
call
to
publish
the
package
to
the
gitlab
api
api
for
the
package,
composer
endpoint
and
normally
you
should
you
do
this
yourself,
but
it
does
everything
for
you
easily.
So
now
let
me
return
my
my
normal
ci
file
so,
like
I
said
previously,
basically,
what
I'm
doing
here
is
to
test
my
package
first
to
make
sure
everything
is
working.
Fine
then
the
next
thing
is
to
publish
and
I'm
only
publishing
whenever
a
match
is
done
to
master
now.
A
I
decided
to
run
my
pipeline
so
that
it
publishes
my
application
running
on
master
yep.
Now.
What
it
will
do
here
first,
is
to
run
my
test
stage,
which
is
simply
composer
update
and
php
dash
file,
run
the
test.h
dot
php
file,
and
that
way
I
know.
Okay,
everything
is
working.
Fine,
then,
on
the
publish
stage
it
publishes
my
package
to
the
composer
repository
register
within
gitlab,
and
your
packages
will
be
published
on
that.
If
you
go
to
the
menu
of
gitlab
on
the
left,
we
have
packages
and
registries.
A
Then
you
go
to
package
registry.
So
while
we
wait
for
this
to
run,
let
me
show
you
quickly
here
you
see
we
have
different
package
repositories:
composer
conan,
marvin,
npm,
nougats
and
piper.
Then
this
is
for
composer.
This
is
the
one
that
I
just
published
that
it's
publishing
once
this
is
a
previously
published
one
once
this
ci
is
done.
If
I've
made
any
new
updates,
it's
going
to
update
it.
Now,
let's
see
what
it
looks
like
now,
this
was
published
two
hours
ago
and
it
was
published
to
the
devs
master
branch.
A
You
can
decide
to
use
a
tag
like
version.
One
or
whatever
it
is,
but
here
I'm
choosing
to
use
the
master
branch.
Now,
it's
showing
me
how
to
use
it
here.
If
you
want
to
use
this
particular
package
in
your
composer
registry,
you
need
to
copy
this
particular
path
into
your
registry,
and
you
must
mention
into
your
composer.json
file,
and
you
must
mention
the
package
name
now.
A
Let's
see
the
progress
of
our
pipeline,
how
it's
done
so,
basically,
here
everything
that's
done
it,
it
simply
checks
and
run.
My
does
composer
update
and
it
runs
my
test
file
which
basically
displays
a
code
and
the
author
of
the
code.
A
A
Your
in
your
settings
ci
variable
file.
If
you
notice
here,
I
have
a
variable
name,
user
and
a
token
now
in
my
project.
What
I
do
with
both
of
this
is
instead
of
having
to
have
code,
my
composer
authentication,
the
authentication
I
need
for
composer
to
be
able
to
communicate
with
gitlab
into
off.json,
which
is
the
normal
one
composer
recognizes
I've
decided
to
just
use
composer
config
instead.
A
So
this
is
the
most
advanced
methods
to
use
when
you
are
using
credentials
for
composer
on
production
systems.
So
now
to
use
my
package
here,
I
create
a
composer.json
file
specifying
the
repository
I
want
to
prove
from
just
like
it
was
shown
in
the
package
details
earlier
and
required
the
package
I
want
to
use,
and
if
you
notice
here,
I
specify
the
package
name,
I
will
package.
Slash
quote
that's
dependent
on
how
you
specify
it
in
the
when
you're,
creating
the
package,
and
I
specify
what
version
I'm
using,
which
is
devmaster.
A
Gitlab.Cimo
file
in
my
gitlabs
gitlab
cimo
file.
I
do
the
two
things
that
first,
the
first
one
is
to
set
up
the
authentication.
That
composer
will
use
to
authenticate
with
the
gitlab
composer
repository
registry
now,
and
you
can
do
that
by
using
composer
config
specify
what
configuration
is
going
to
modify
in
composer's
config
and
specify
that
it
should
use
gitlab.com.
A
A
Gitlab.Com
as
the
repositories
will
be
pulling
from,
and
if
you
remember
in
my
ci
variable,
I
specified
a
user
and
a
token.
This
token
will
be
your
private
access
token
that
you've
created
from
settings,
especially
when
you
are
using
2fa.
You
cannot
use
your
normal
password
now.
The
next
thing
I
do
here
is
to
run
composer
update
once
composer
is
authenticated.
A
Now
my
index.php
file
is
quite
similar
to
the
test.php
file
in
my
package,
and
all
it
does
is
to
require
the
require
autoload
use
the
code
class
from
the
package
and
display
code
and,
if
there's
an
error,
to
display
an
error.
But
basically
I
want
it
to
say
social,
author
one
said
and
so
on.
Now,
let's
that's
basically
what
my
this
php
project
is
doing
now,
let's
run
this
quickly
in
let's
make
a
little
change
in
my
project
and
see
instead
of
just
seeing
auto
once
said,
yeah.
A
A
A
A
Everything
works
now,
as
of
now
composer
repository
is
only
supported
on
13.2
for
premium
and
ultimate
customers,
but
there
are
already
works
being
done
for
it
to
be
available
right
from
core
to
black,
open
call,
which
means
for
everyone.
I
think
it's
in
13.3,
but
very
soon
it
should
be
available
for
everyone
to
use
okay
yeah.
It
has
already
authenticated,
as
you
can
see
here,
it
has
already
authenticated
with
gitlab.com
and
it's
updating
my
composer
repositories
already.
A
This
makes
life
much
easier
for
php
developers,
especially
those
working
in
organizations
where
they
can't
host
the
repositories
publicly,
and
previously,
all
you
had
to
do
was
use
the
projects
directly
and
specify
how
composer
authenticates,
with
with
your
projects
within
composer
or
have
some
some
costume
mechanism
with
these
in
gitlab.
It
makes
it
much
more
easier
for
you
to
have
a
dedicated
dependency
and
even
tag
and
version
it
as
you
want.
Oh
awesome,
our
job
has
finished
running,
as
you
can
see
here,
the
change
we
made
it's
here.
A
It
says
quote
of
the
day.
Brent
brown
once
said
you
don't
have
to
do
all
of
it
alone.
We
were
never
meant
to.
I
hope
you
enjoyed
this
demo
and
look
forward
to
you
using
more
of
the
composer
repository
on
gitlab.
Thank
you
very
much
for
joining
this
session.