►
A
A
So
the
the
first
section
here
looks
like
I
have
the
wrong
title
on
this
issue.
So
I'll
fix
that
later,
but
the
like,
I
was
saying
this
is
a
sync
update
experiment.
So
I've
got
the
schedule
for
the
next
upcoming
updates
for
the
next
three
weeks.
So
if
you
care
to
join
those,
come
on
and
hear
about
what
we're
doing
and
ask
all
the
questions
you
want.
A
So
as
far
as
the
updates
for
this
week,
the
I'm
continuing
to
work
on
the
secure
files
in
bc
and
so
to
give
a
little
bit
of
context.
This
is
a
feature.
Secure
files
is
a
feature
that
I've
been
working
on.
That
essentially
creates
the
ability
to
have
like
binary
files
as
ci
variables,
and
so
the
point
of
this
is
to
make
it
easy
for
mobile
teams
to
upload
their
provisioning
profiles
and
key
store
files,
and
things
like
that
into
gitlab
in
a
way
that
they
can
control
them.
A
Much
like
they
would
a
ci
variable,
and
so
so
that's
what
that's.
What
this
feature
is
for.
There's
a
bunch
of
work
here,
kind
of
in
progress
around
the
mdc,
and
so
I'm
continuing
to
work
through
this,
and
hopefully
we'll
get
this
to
a
state
soon,
where
we
can
start
testing
some
projects
on
gitlab.com.
A
But
the
the
big
kind
of
thing
that
I
worked
on
this
week
was
looking
into
excuse
me
using
this
secure
files
feature
with
fastlane
match
and
so
to
give
a
bit
more
context.
There.
I've
got
a
link
to
fastlane
and
what
fastlane
is
is
a
open
source
tool
that
a
lot
of
mobile
teams
use
to
make
the
build
and
deploy
process
easier.
A
It
kind
of
abstracts
some
of
the
complexity
around
like
building
and
deploying
to
the
app
stores
and
things
like
that,
and
one
of
the
tools
is
part
of
fastlane
as
a
tool
called
match,
which
is
which
is
focused
on
the
certificates
and
provisioning
profiles
and
like
making
that
process
a
lot
easier
for
something
like
fastlane
match.
You
would
end
up
with
different
certs
and
profiles
on
different
developers,
machines
and
it
could
be
kind
of
a
mess,
and
you
don't
know
which,
which
cert
or
profile
is
being
used.
A
When
you're
deploying
your
app
to
the
app
store
and
then
maybe
a
developer
leaves,
and
then
you
lose
that
profile
and
everything
breaks.
So
what
match
aims
to
do
is
to
like
centralize
that
data
into
one
back
end
so
that
you
can.
You
can
have
some
consistency
there
and
then
you
can
share
those
certain
profiles
across
developer
machines
and
then
you
can
like
actually
build
that
into
your
deploy
pipelines
as
well.
A
So
right
now,
fastlane
match
offers
three
different
backend
configurations,
so
you
can
use
a
git
backend,
google
cloud
and
aws
s3,
and
these
are
these
work.
Fine
I've
used.
So
I
built
a
demo
app,
and
this
is
kind
of
the
configuration
that
I
use
to
set
it
up
for
using
a
git
back
end.
So
I
just
give
it
a
it's
a
separate
project,
a
separate
repository
and
it
stores
the
the
certificates
in
there
in
an
encrypted
format
and
then
you're
going
to
want
to
make
that
project
private.
A
A
So
you
know
sort
of
an
idea
of
what
that
might
look
like
is
this
is
my
configuration
before,
and
this
is
what
it
would
look
like
after
so
I
could
just
give
it
the
the
project
id
or
the
project
identifier
and
then
just
tell
it.
I
want
to
use
scalab
secure
files
and
then
what
that
would
do
is
any
time
we
go
to
run
a
fast
lane
build
or
a
fast
lane
deploy
it'll.
A
It
uses
the
match
process
as
part
of
that
and
then
it'll
just
pull
in
those
certificates
from
from
the
secure
file
back
end,
and
so
far
I've
am
about
halfway
through
kind
of
working
up
a
pull
request
for
this,
but
the
the
apis
are
very
similar.
So
in
all
of
these
implementations
they
essentially
have
a
download
and
upload
and
delete
api,
and
that's
exactly
how
the
api
works
for
secure
files
today.
So
it
should.
It
should
pretty
much
match
exactly
the
functionality
that
we
would
need
to
have
there.
A
So
I'm
going
to
continue
to
work
through
that
and
and
hopefully
have
a
full
request
up
into
the
fastlane
project
next
week.
So
that
is
pretty
much
covers
that
so
in
my
up
next
section.
Basically,
the
things
I'm
shooting
for
next
week
is
to
to
keep
making
progress
on
that
mvc
roll
out
and
then
have
a
a
pull
request
into
fastlane
for
next
week.
So
that's
what
I've
got
for
today,
any
any
questions
from
the
audience.