►
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,
everyone
and
welcome
to
the
distribution
weekly
demo
for
august
12th,
2021,
I'm
doing
the
demo
today
and
the
item
I'm
demoing
is
what
I
have
spent
some
time
working
on
this
week
as
a
deliverable
and
that's
around
adding
the
ability
to
provide
smtp
credentials
to
the
git
lab
application
via
encrypted
secrets.
A
This
is
targeted
for
use
in
source
installs
in
omnibus.
In
on
the
cloud
native
side,
we
already
make
use
of
the
kubernetes
secrets
to
provide
something
like
this
and
rely
on
the
underlying
kubernetes
secrets,
infrastructure
but
yeah.
This
is
for
other
cases,
and
this
is
still
a
work
in
progress.
Merge
request,
but
I
was
just
gonna
walk
through
demoing
how
it
ends
up
working,
so
I
have
an
instances
just
booting
up
here,
a
local
docker
instance.
A
That's
making
use
of
this
development,
mr,
and
once
it
is
fully
up
we'll
be
able
to
start
working
with
it.
Okay,
so
it
is
up,
should
be
available
locally.
On
my
machine.
A
And
we
will
go
ahead
and
this
is
not
configured
with
anything
at
the
moment.
So,
just
a
default
omnibus,
docker
image
running
we'll
go
ahead
and
change
the
config
file
and
enable
smtp.
A
A
To
show
the
password
in
in
the
demo,
because
it'll
be
it'll,
be
swapped
out
at
the
end
of
the
meeting.
So
I'm
going
to
point
this
at
mail
gun.
Initially,
I'm
going
to
not
I'm
just
going
to
show
it
without
the
encrypted
settings.
So
when
we're
regularly
setting
this
up
in
omnibus,
we
have
to
put
everything
here
in
the
gitlab
rb,
including
the
username
and
password,
so
I'll
go
ahead
and
throw
in
the
config
for
my
mail
gun
up
here.
A
The
github
yml
in
the
rails
project
actually
doesn't
have
any
smtp
settings
available
in
it
for
smtp
in
the
rails,
app.
What
we
rely
on
is
actually
introducing
users
or
when
you're
a
source
installer
supposed
to
introduce
a
new
initializer
into
the
program
that
sets
up
rails,
active
mailer
configuration
in
the
case
of
charts
and
omnibus.
A
We
build
this
initializer
ourselves
and
throw
it
into
the
folder.
So
I'll
just
show
you
that
file.
Basically,
so
you
can
see
what
the
setup
looks
like.
That
is
a
little
weird.
I
think
it's
the
only
that
might
be
the
only
one
we
do
that
way,
where
the
omnibus
or
charts
actually
are
like
adding
something
to
like
the
code
directories.
A
So
it's
actually
gets
added
in
the
omnibus
embedded
services.
A
A
A
A
Well,
actually,
you
can
see
see
what
it
ends
up
doing
so
when
you
don't
provide
it
through
on
your
bus.
It
now
pulls
from
these
in-app
secrets,
which
we
don't
have
provided,
so
these
will
actually
be
returning
mail.
A
So
if
we
try
to
send
an
email
right
now
we
get
an
auth
error,
but
we're
going
to
go
ahead
and
set
these
up
so
in
in
our
encrypted
secrets
that
we
introduced
last
year
for
ldap
we
kind
of
set
set
up
a
standard
for
how
we
were
doing
these,
so
these
smtp
or
we
we
set
up
not
a
standard
but
exam
precedence
for
how
we
were
allowing
these
users
to
edit
these
secrets,
so
we're
doing
it
through
the
rake
tasks
at
the
moment.
A
This
rape
task,
the
one
we
added
last
year
for
ldap
credentials,
was
under
just
this
ldap
syntax.
So
we've
added
this
one
here
and
then
you
can
specify
as
a
flag
which
text
editor
you're
gonna
use.
I
think
in
the
docker
image
by
default
we
already
have
the
editor
flag
set
in
the
environment,
so
I
should
be
able
to
just
run
the
rig
command
and
be
presented
with
an
editor
for.
A
In
the
shared
storage
directory
under
encrypted
settings,
this
is
a
configurable
path,
but
this
is
also
where
the
ldap
one
is
usually
stored.
So
if
it's
stored
here
as
encrypted
file
that
the
application
loads
and
decrypts
with
the
encrypted
settings
key,
which
was
something
we
added
last
year
encrypted
setting
space
key.
A
So
once
you've
got
it
set,
you
would
in
order
for
it
to
actually
be
picked
up
by
the
application.
You'd
have
to
restart
the
application
in
the
case
of
email,
only
sidekick
makes
use
of
it,
so
we'd
only
have
to
restart
sidekick
for
it
to
start
making
use
of
these
new
settings,
but
a
few
more
things
on
the
command.
These
are
all
the
same
as
the
ldap
one.
There's
a
show
command.
A
If
you
spell
it
right
that
you
can
pipe
the
input
into
for
to
write
it,
that
you
have
it
the
plain
text
coming
from
like
another
key
management
system
or
secret
management
system,
you
can
be
you
know,
piping
from
that
system
into
this
system.
That's
how
we
kind
of
add
support
for
people
bringing
in
these
things
from
from
other
from
other
systems
where
they
already
have
these
secrets,
as
they
could
be.
A
You
know
if
their
system
supports
like
listeners
for
like
on
change
from
the
server
or
something
like
that
that
they
can.
Whenever
the
key
changes,
they
can
have
a
script
that
then
pipes
the
key
in
to
the
to
our
version
of
the
secrets,
and
then
they
can
restart
psychic
or
flight
some
flag.
They
didn't
use,
restart
or
something
like
that.
A
A
A
Like
this,
so
within
within
the
running
rails,
application
they've
been
decrypted
and
are
available
just
as
their
normal.
A
A
A
And
adding
in
because
we
don't
have
an
existing
place
for
smtp
secrets,
because
there
are
smtp
settings
because
they're
a
whole
new
file
that
we
expect
omnibus
or
charts
to
add
adding
in
a
new
config.
That
has
support
for
fetching
from
the
secrets.
If
you
haven't
provided
any
anything
else,
and
then
we
did
because
this
is
only
the
second
command
we
we
added
in
this,
mr
the
the
ldap
one,
had
all
the
logic
for
what
what
the
rate
commands
look
like.
A
So
everything
that
was
common
that
would
be
used
among
multiple
commands
got
extracted
into
this
base
file
and
then
the
end
result
is
that
new
commands
are
like
kind
of
basically
look
like
this,
where
you
just
set
what
the
command
name
is
the
display
name
where
it's
getting
its
encrypted
secrets
from
and
then
what
the
default
template
is
and
then
set
up
the
rake
task
and
then
some
tests
yeah.
A
So
on
this,
mr,
the
remaining
items
are
docs
and
usage
ping,
and
then
this
one
will
be
ready
for
review
and
then
it
needs
an
accompanying.
Mr
on
the
omnibus
side,
which
I
thought
we've
been
working
on,
that
just
you
know
makes
use
of
those
actually
adds
what
we
saw.
Those
secrets
settings
to
smtp
settings
file,
and
that
is
it.
B
That
looks
like
great
iteration
from
the
previous
work
picturing,
the
next
one,
even
being
simpler,
based
on
what
you
showed
in
the
mr,
it's
nice.