►
Description
In this update Shekhar walks you through the features added to the custom control plane, including:
1. Support for authentication and authorisation
2. Containers now have attached volumes
3. Ability to open ports to aid in web development
4. Orchestrate backends for the new VS Code based Web IDE.
Chapters
0:00 Overview
0:49 Authentication / authorisation
1:41 Attaching volumes
2:00 Open ports
3:03 Attaching to the web IDE
4:20 What is next
A
Hello,
welcome
to
the
update
for
the
server
runtime
sag
for
the
week
of
19th
October,
so
made
quite
a
lot
of
progress.
This
week,
we're
gonna
be
focused
on
authentication,
so
what
we
were
missing
is
authentication
for
the
Ides.
So
so
far
we
didn't
support
authentication
authorization.
We
have
that
now.
A
A
What
we
also
have
is
ability
to
open
port
so
as
you're
doing
web
development,
you
can
open
port
so
that
you
can
actually
see
the
application
that
you're
developing
and
then.
Finally,
you
can
also
use
the
new
gitlab
web
IDE,
along
with
the
custom
control
plane,
so
I'm
going
to
show
you
these
features
now.
A
Okay,
so
the
first
thing
I
want
to
show
you
is
that
we've
implemented
full
authentication
and
authorization
now
so
I've
already
spun
up
an
IDE.
So
if
I
go
ahead
and
navigate
to
that
IDE,
it
now
shows
me
an
Authentication
screen.
So
I
can
go
ahead
and
sign
in
with
my
gitlab
credentials
and
as
long
as
I
have
access
to
the
IDE.
It's
going
to
start
showing
up,
so
we
do
authorization
as
well.
That
means
that
if
you
spun
up
the
ID,
you
have
access,
but
we
can
extend
the
model
in
the
future.
A
If
you
wanted
to
to
also
give
access
to
other
developers
in
the
team,
you
know
give
your
ID
access
to
other
developers
of
the
team.
Now,
if
I
go
ahead
and
navigate
to
this
in
a
separate
window
and
and
as
a
different
user
I
don't
have
access,
so
this
user
doesn't
have
access
and
therefore
we
get
a
big
500
internal
server.
A
The
second
thing
I
want
to
show
you
is
that
we
now
are
attaching
volumes.
So
if
I
go
ahead
and
check
here,
you
can
see
that
I
have
a
volume
attached
onto
home
workspaces.
So
that's!
This
is
a
two
gig
volume
that
we
attached
by
default,
and
so
now
people
can
actually
store
that
code
on
the
Ides
as
well.
A
I
also
want
to
show
you
the
fact
that
now
we've
added
the
ability
to
open
up
Port.
So
in
your
gitlab
experience
yaml,
you
can
specify
the
ports
that
you
want
to
open
up
and,
of
course,
in
my
code
and
this
this
is
very
useful
for
web
development.
So
as
I'm
developing
and
updating
my
code,
I
can
go
ahead
and
see
my
changes
right.
So
in
my
code,
I'm
starting
a
web
server
on
Port
80
90..
So
if
I
go
ahead
and
say,
go
on
main.go
that
goes
and
starts
up
the
web
server.
A
So
now
I
actually
want
to
see
what
what
you
know
what
I've
created
and
so
I
can
go
ahead
and
all
I
need
to
do
is
really
update
the
port
here.
So
I
can
go
ahead
and
say:
80
90
and
if
I
go
up
update
the
port
you'll
see
that
it
goes
ahead
and
shows
me
my
the
message
that
I've
put
in
my
course
there
I
can
make
changes
very
quickly.
A
So
the
ability
to
open
up
ports
really
makes
it
easy
to
do
a
web
development.
The
last
thing
I
want
to
show
you
is
that
we're
also
supporting
now
remote
environments.
So
now
the
web
IDE
can
connect
to
things
that
have
been
orchestrated
by
this
custom
control
plane.
So
I'm
going
to
go
ahead
and
spin
up
a
new
environment
for
myself,
and
so
this
environment
is
going
to
be
a
specific
image
that
enables
me
to
use
a
web
ID
I'm,
going
to
pause
here
and
wait
for
the
environment
to
complete
it.
A
So
the
environment
has
started
up
now.
I
could
go
ahead
and
sign
in
with
my
credentials,
and
as
you
see
it
says
that
your
remote
development
environment
is
ready.
You
can
now
log
in
with
the
web
IDE,
so
I'm
going
to
go
ahead
and
click
on
the
button
here
and
that
on
the
link-
and
you
can
see
that
it,
it
pre-populates
all
the
values
for
me.
So
all
I
need
to
do
is
now
copy.
A
The
token
put
it
in
and
say
start
web
IDE,
and
this
goes
ahead
and
starts
the
gitlab
IDE
and
connects
to
my
remote
environment
and
in
a
few
seconds,
I
should
have
full
access
and
I
can
explore
my
files.
It's
clone
the
repository
as
well.
I
can
explore
my
files
and
I
could
also
go
ahead
and
run
my
program
because
I
didn't
now
have
access
to
the
download.
A
So,
thanks
for
listening
to
this
next
week,
I'm
going
to
be
focusing
on
quite
a
lot
of
cleanup,
so
cleaning
up
tests
making
sure
that
the
documentation
is
up
to
speed
I
also
want
to
explore
the
use
of
Google
as
an
a
DNS
provider.
So
right
now,
I've
been
using
GoDaddy
as
a
DNS
provider,
but
I
want
to
support
other
DNS
providers
as
well.
So
those
are
the
things
I'm
working
on.
Thank
you
for
listening.