►
From YouTube: Proposed Doctor Script for the GitLab Handbook Project
Description
A first iteration of a tool help ensure that you've met the required dependencies before trying to run handbook scripts.
See the following MR for more:
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/65312
A
Hello,
I'm
chase
southard,
I'm
the
engineering
manager
for
the
progressive
delivery
team.
What
I'd
like
to
share
with
you
today
is
a
tool
that
I
put
together
called
doctor
for
the
handbook
project.
This
this
tool
might
be
helpful
in
validating
that
you
have
all
the
proper
working
versions
of
the
dependencies
required
to
run
the
handbook
locally.
There's
a
handbook
page
that
outlines
the
installation
process
of
all
the
required
dependencies,
but
there's
no
process
yet
to
check
that
you
have
all
the
right
pieces
and,
as
I've
seen
it
in.
A
So
what
I'd
like
to
share
with
you
today
is
this
script
called
doctor
that
I've
proposed
to
add
to
the
the
handbook
and
what
doctor
does
is
it
performs
checks
of
the
installation
of
ruby
and
those
related
tools?
Currently,
that's
all
it
does,
but
it
can
be
easily
extended
to
check
for
other
dependencies
that
are
required
for
like
node.js
or
yarn.
This
is
just
the
first
iteration
and
a
place
to
start
and
it
attempts
to
solve
the
problems
that
I've
seen
helping
other
people
through
the
challenges
of
running
the
handbook
locally.
A
And
the
first
thing
we
get
back
outside
of
the
preamble
there,
the
beginning
is
that
it
says
you
have
a
ruby
version
mismatch
and
what
that's
saying
is
that
the
version
of
ruby
you're
running
in
this
case
265
does
not
meet
the
the
version
that
is
required
for
the
handbook
to
run.
There
is
a
there
is
a
version
file
in
the
handbook
that
describes
what
version
is
required
and
that's
what
I'm
checking
against.
A
So
what
I'm
going
to
do
here
is
I'm
going
to
install
that
version
of
ruby,
asdf,
install
ruby,
266
and
so
now,
what's
going
to
happen,
is
we're
going
to
download
and
install
compile
ruby,
I'm
using
a
tool
called
asdf?
You
might
be
using
a
tool
called
rvm
or
rbnv,
even
that's
kind
of
secondary
to
what
I'm
trying
to
show
here.
A
Proceed:
okay,
so
some
time
has
passed
and
we've
installed
ruby
266
here
and
then
we've
got
some
errors
that
we're
just
going
to
ignore
from
the
moment.
Everything
is
fine,
I'm
going
to
make
sure
that
we
are
running
the
correct
version
of
ruby.
That
is
has
just
been
installed,
and
here
we
can
see
in
my
prompt
that
that's
true
I'm
going
to
clear
the
screen
to
make
things
a
little
more
legible
and
then
we'll
run
bin
doctor
again.
A
Okay,
great
new
information,
I'll
scroll
up
here
it
says
you
have
the
proper
version
of
ruby,
installed
and
or
selected
great
check.
The
ruby
library
manager
called
bundler
has
been
installed
check.
We
have
some
warnings
here
about
the
those,
the
versions
of
bundler
and
things
and
some
of
the
dependencies
which
we
don't
need
to
worry
about
at
the
moment.
A
A
Everything's
green,
no
error
messages
which
is
great,
and
I'm
going
to
go
ahead
and
clear
the
screen
again
just
to
make
it
a
little
bit
more
tidy,
so
clear
and
then
so
now
that
we
know
we
have
the
right
version
of
ruby,
running
bundler
has
been
installed
and
we've
gone
through
some
cycles.
That
says
all
of
our
bundled
gems
are
up
to
date.
So,
let's
just
run
doctor
one
more
time,
just
to
be
sure,
check
more
check.
Mark
your
gym
files.
Dependencies
are
satisfied,
so
we
have
to
install
anything
new.
Everything
is
good.
A
You
can
go
about
the
rest
of
your
day
and
do
whatever
tasks
you're
going
to
do
here
inside
the
handbook
and
so
so
there.
I
think
this
is
a
great
first
iteration
happy
to
take
feedback
and
and
see
this
become
useful
for
people
who
may
not
be
engineers
in
the
gitlab
team
or
anyone
else
for
that
matter.