►
From YouTube: Developer Experience Office Hours: Front-End Frameworks
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
A
Good
morning
good
afternoon
good
evening
and
welcome
to
another
episode
of
the
developer
experience
office
hours
here
on
openshift
tv,
I
am
chris
short
executive
producer
of
this
thing.
We
call
open
shift
tv
and
I
am
joined
by
three
of
our
most
wonderful
developer
experience,
people,
ryan,
jarvan,
natali,
vento
and
joel
lorde.
Welcome
to
the
show
ryan
your
video's
already
frozen.
Let
me.
A
D
Yeah,
joel,
you
want
to
introduce
yourself
for
the
audience.
Please
hi
everyone.
Thank
you,
chris
very
happy
to
be
here.
I
work
as
developer
advocates
in
the
same
team
as
both
natalie
and
ryan,
so
yeah.
Basically,
our
job
is
here
to
try
to
make
developers
like
you,
your
life,
easier
yeah.
Well,
I
mainly
focus
on
javascript
stuff,
which
is,
which
is
why
I
guess
I
was
invited
today.
D
So
a
lot
of
I've
been
doing
a
lot
of
javascript
in
the
last
many
years,
both
front-end
and
back-end.
I
really
love
javascript
as
a
language
like
I
think,
it's
nice,
it's
versatile!
You
can
use
it
everywhere.
So
yeah,
that's
that's
pretty
much
it
about
me.
B
C
Awesome
finally
got
my
video.
Hopefully
my
video
is
coming
through
now.
C
You
ryan
jarvanine,
you
can
find
me
most
places
online
as
ryan
jay,
I'm
also
a
developer
advocate
thanks
to
natalie,
joel
and
chris
for
joining
us
here
today.
I
think
the
main
topic
that
we're
hoping
to
cover
is
just
to
show
off
how
to
use
some
front-end
developer
frameworks
in
our
new
developer,
sandbox
environment.
C
So
you
could
try.
This
really
should
work
on
any
open
shift,
whether
you
have
code
ready,
containers
or
learn.openshift,
or
any
of
them
should
work
the
same
on
just
about
any
system,
and
the
nice
thing
about
front-end
frameworks
is
usually
when
you
go
to
roll
out
a
release,
you
could
basically
host
them
on
any
platform.
They're,
not
you
know
tied
to
running
only
on
kubernetes.
C
You
could
basically
host
them
out
of
a
s3
bucket
to
some
extent,
because
they're
just
static
html,
so
we'll
try
to
get
to
that
as
a
outcome
later
on
in
the
show
doing
a
deployment
that
packages
it
up
in
the
dist,
folder
or
or,
however,
this
framework
happens
to
work
and
then
we'll
roll
out
a
deploy,
hopefully
with
a
nginx
package.
C
I
didn't
practice
that
step,
so
I
may
need
some
pointers
from
from
joel.
I
think
he's
done
it
once
or
twice
before,
but
I
think
the
first
step
I
wanted
to
start
off
with
was
deploying
a
react.
Js
front
end
and
showing
how
basically,
what
a
standard
dev
workflow
might
look
like,
as
as
far
as
your
initial
iteration
on
a
react.js
project
for
folks
who
haven't
seen
that,
but
have
the
whole
thing
containerized
any
questions
about
that
or
any
thoughts.
A
C
B
C
I
don't
have
the
chat
open
currently,
so
if,
if
other
folks
can
keep
an
eye
on
on
chat
for
me
and
for
folks
in
chat,
thank
you
for
joining
us
here
as
well.
If
you
have
any
other
topics,
you
would
like
to
see
on
the
developer
experience
office
hour.
Definitely
let
us
know
we
also
have
a
feedback
form.
C
We
could
post
a
link
into
chat
for
you
if
you
have
other
feedback
for
us,
definitely
fill
out
that
that
form
there
and
let
us
know
of
topics
that
you're
interested
in
seeing
and
let
me
hit
the
share
desktop.
C
C
C
Once
you
log
in
with
your
red
hat
account,
you
should
be
able
to
sign
up
for
the
dead,
the
sandbox
environment
and
then
the
the
red
link
there
will
change
to
launch
sandbox,
there's
one
other
step
signing
in
through
some
access
credentials,
and
you
just
choose
the
developer
sandbox
button
on
the
on
the
sign
in
page
okay.
So
this
is
so
far.
I
just
have
an
empty
project,
ryan,
j
dev,
and
I
think
I'm
going
to
open
up.
Let's
see
if
I
can
open
up
a
terminal
locally
here.
C
C
C
B
C
C
Let's
do
get
remote
dash
v
cool
set
url,
and
this
is
origin.
C
B
C
Cool,
hopefully
that
works,
so
I
have
my
example,
repo
and
I'm
going
to
try
deploying
that.
C
We'll
need
to
add
in
templates
as
the
type
and
there's
one
it's
like:
we've
got
we're
gonna
get
postgres
or
mongodb
automatically
added
cool.
Here
we
go.
If
you
had
builder
image,
then
you'll
see
just
the
node.js
without
any
any
add-ons,
so
we
could
do
create
application.
C
It
looks
like
this
is
hosted
on
node.js
12,
with
a
ubi
image.
There's
a
couple.
Other
choices
in
here.
A
B
A
B
C
C
C
Are
these
basically
just
using
the
react?
Scripts
generate
to
start
out
yeah
yeah
skeleton
for
each
of
these
or
exactly.
D
If,
if
you
scroll
down
a
little
bit,
you'll
see,
there's
there's
links
to
two
blog
posts
there,
that
kind
of
describe
a
little
bit
into
a
little
bit
more
details.
But
basically
I
was
having
issues
trying
to
build
rootless
containers,
so
this
basically
describes
how
to
build
a
rootless
container
with
with
various
popular
javascript
frameworks.
So
I
I
did
examples
for
all
three
major
ones,
so
react
view
and
angular
and
basically
they're
all
using
the
skeleton
application
directly
from
the
cli,
so
create
react
app
for
react
view
cli.
D
I
can't
remember
the
exact
syntax
and
even
less
with
angular,
but
just
a
basic
application.
Remove
the
the
you
know
the
the
landing
screen
that
is
there
and
just
replaced
it
with
the
same
screen
that
reads
up
some
environment
variables
in
each
one
of
those
projects.
So
really
it's
almost
like
identical
to
the
the
skeleton
application.
I
just
made
sure
that
they
all
kind
of
have
that
same.
Look.
C
Nice,
that's
really
cool.
I
like
the
being
able
to
get
things
from
the
environment
into
a
front-end
application,
is
always
a
kind
of
a
tricky
process
so
glad
you
have
an
example.
That's
super
clear.
D
I've
and
and
if
you
ever
need
to
build
a
container
image
from
you,
can
use
those
and
and
basically
there
are
instructions,
but
essentially
it
just
breaks
down
to
this
copy.
The
the
docker
file.
That's
there
and
it's
generic
enough
that
you
can
pretty
much
use
it
in
any
react.
Angular
or
vue.js
projects.
C
C
Awesome,
cool
yeah:
this
is
kind
of
what
I
was
hoping
and
so
we'll
see.
I
tested
out
the
react
one
and
have
a
little
bit
more
confidence
that
that
one's
going
to
succeed
so
we'll
start
there.
I
didn't
have
a
successful
test
of
the
angular
one
last
night,
but
we
could
give
it
another
try
and
see
if
we
could
pack
it
together.
Potentially
I'm
really
interested
in
looking
at
the
view,
one
as
well,
and
I
really
like
the
idea
of
being
able
to
investigate
how
to
publish
selected
information
from
the
environment.
C
That's
a
really
nice
thing
to
have
illustrated.
I
was
thinking
of
doing
like
a
config
map
or
something
and
just
mounting
a
bunch
of
config
as
a
json
file,
so
that
that
json
file
could
be
referenced.
C
Maybe,
but
I
don't
know
yeah
we'll
we'll
see
if
we
can
have
time
to
look
at
environment
variables
as
well.
I
know
I'm
going
to
have
to
do
one
small
modification
on
this
one
in
order
to
get
so
so
far,
I've
set
the
react
context
der
here.
I'm
going
to
set
to
react
project.
A
C
Okay,
right
that
looks
like
it's
working,
I'm
gonna
leave
the
secret
as
is,
but
we
could
potentially
have
a
you
know,
a
hash
of
of
data
stored
somewhere
that
we
wanted
to
mount
into
this
container.
C
We
can
call
this
surefronted,
I'm
just
going
to
call
the
app
front
end
and
I'm
going
to
name
this
front
end
dash,
react
and
we'll
use
a
standard
deployment
instead
of
a
deployment
config
for
this
one,
since
I'm
going
to
use
kind
of
like
a
development
style
mode,
also,
there's
an
option
for
creating
a
route.
C
C
Route
to
8080.
that
that
is
the
default,
that's
what
I
did
last
night
and
then
I
just
made
tons
of
edits,
and
so
I
can
go
that
route.
Let's
add
the
let's
add
the
route
we'll
leave
it
in
that'll
produce
a
couple
errors,
but
we
can
work
through
that,
assuming
I
can
log
in
via
the
command
line.
So
while
this
build
is
running
here
should
be
able
to
click
on
this
and
see
that
there
is
currently
a
build
running,
and
this
is
going
to
do
things
like
it
should
do.
C
Npm,
install
and
a
couple
other
things
unless
all
the
dependencies
are
already
committed
into
the
node
modules.
Folder,
I
think,
is
this
one
using
npm
or
yarn
I
saw
one
of
them
was
using
yarn.
Take
a
look
in
here:
oh
there
is
a
yarn.lock,
but
we
also
have
a
package.json,
and
hopefully
you
can
see
in
here.
C
D
If
you're
not
familiar
with
react
application,
basically,
what
this
does
is
that
it
starts
a
development
server
which
is
running
on
node.js
and
it
watches
for
file
and
changes,
and
it
will
do
hot
reloads
on
your
browser.
So,
basically,
as
soon
as
you
edit,
the
code,
you
will
see
the
updates
appear
in
inside
your
browser.
So
it's
it's.
It's
a
very
convenient
way
to
build
applications
always
like
live
reload.
C
A
D
Listen
before
I
start
doing
javascript
I
used
to
do
php
many
many
years
ago
and
I
remember
trying
to
do
a
change.
Send
that
to
the
ftp
server
f5
f5
f5.
D
Those
days
so
much.
C
All
right,
so
it
looks
like
this.
This
app
is
still
lit
up
light
blue,
so
it's
in
a
pending
state.
I'm
not
sure.
If
that's
because
it
looks
like
yeah
build
is
still.
D
Running
yeah,
all
right,
so
why
don't
you
expect
it
to
take?
Maybe
five
minutes
to
down
to
create
a
react
application
you
basically
have
to
download
half
of
the
internet,
so
it
can
take
a
little
bit
of
time.
There.
C
Well,
while
this
is
running
I'm
going
to
run
oc
edit
on
our
service,
it
looks
like
I
ran
oc,
get
svc
to
list
the
services
we
have.
One
for
front
end
react,
so
I
can
run
oc
edit
on
this
service
and
take
a
look
at
what
port
number
it's
currently
configured
for,
looks
like
we
have
8080
in
here,
and
we
want
to
target
port
3000
in
the
container.
C
C
B
C
Okay,
I
usually
do
it
from
the
ui,
but
yeah
yeah
this.
This
would
definitely
be
easier
from
the
ui.
I
don't
necessarily
recommend
running
oc
edit
and
just
hacking
away
at
objects,
but
this
is
one
kind
of
way
to
interact
with
these
resources.
D
C
But
here's
here's
the
same
thing
already
updated
here
on
the
in
the
ui
and
if
I
click
on
the
service
here
and
you
can.
C
Yaml
interface,
I
mostly
just
wanted
to
verify
that
that
I
was
able
to
drop
to
the
command
line.
If
I,
if
I
had
to.
C
A
C
Yeah
yeah:
this
should
be
just
about
the
last
step,
so
it'll
push
the
new
the
resulting
image
into
the
open
shift
image
registry.
There
should
just
be
a
hosted
registry
included
with
every
openshift
cluster.
So
a
lot
of
the
traffic
for
your
images
once
built,
are
going
to
be
local
within
that
cluster,
hopefully,
depending
on
how
disparate
your
clusters
are,
so
this
should
do
an
image
push,
and
then
we
should
see
the
result
on
the
topology
view.
B
C
B
C
And
once
this
switches
to
a
darker
blue
it'll,
do
health
checks
confirm
that
the
app
is
responding,
looks
like
it's,
the
right,
color
blue?
So
hopefully
I
have
all
the
port
information
wired
up
accurately.
C
A
C
D
Is
actually
in
the
picking
it
up
from
an
environment
variable?
So
that's
why
it's
just
hard-coded!
For
now!
Oh
okay,.
C
So
a
couple
things
we
could
do
right
off
the
bat
I
can
jump
into
the
terminal.
Also,
this
is
would
also
not
be
recommended
since
I'd
be
adding
changes
into
this
containerized
environment
that
might
get
scaled
up
or
scaled
down
or
restarted
or
re-allocated,
but
I
should
be
able
to
edit
this
public
index.file.
C
C
C
All
right
all
right,
so
I
wrote
that
and
it
was
prob
almost
if
I
had
an
autosave
text,
editor
would
have
been
replicating
all
of
those
changes
into
the
browser.
As
I
was
typing,
but
here
we
got
hello
openshift.tv
to
show
up
and
I
didn't
even
need
to
hit
control
r
or
any
kind
of
reload
like
so
it
happened,
yeah,
yeah,
yeah.
So
a
lot.
A
C
Front
end
frameworks
are
gonna.
Have
this
kind
of
hot
reloading
live
reloading
feature
that
really
really
is
a
massive
productivity
boost,
because,
depending
on
your
editor,
you
might
just
be
able
to
you
know
as
you're
typing
if
it's
auto
saving
those
files
you'll
automatically
see
the
result
reflected
as
you're
working.
C
C
There's
the
pod,
let's
see
well.
B
A
D
Yeah
I'll
answer
that,
yes
with
the
question
mark
natalie,
would
know
more
about
it.
I
believe
natalie,
you
did
something
similar
recently
didn't
you.
B
Yeah,
you
can
run
out
of
the
box
dot
net
core
apps
we're
going
to
support
also
that
net
file.
At
the
moment
we
all
support
that
net
core
which
is
up
to
three,
and
this
is
for
that
net
core.
Then,
if
you
want
to
run
a
native.net
application,
you
could
use
also
two
approach
which
are
the
openshift
container
virtualization.
So
it's
a
windows,
virtual
machine
where
you
can
run
basically
windows
and
your.net
runtimes
in
your
app
or
a
windows
container.
B
Now
we
support
also
windows
containers,
so
in
your
windows,
server
open
sheet
will
be.
We
have
one
windows
note
and
you
can
control
those
application
as
a
windows
container.
Maybe
this
is
the
the
most
difficult
one.
The
easiest
one
would
be
to
use
that
net
core
or
bishop
virtualization
for
that.
But
there
are
many
development
in
progress,
so
I
think
that
net
5
would
be
soon
available.
Also
for
linux.
A
C
I
was
trying
to
run
oc
rsync
from
this
container
into
the
remote
container,
and
it
is,
I
forgot
to
do,
there's
a
like
reverse,
like
a
deny
list
you
can
enter,
so
it
ignores
certain
folders
and
I
usually
always
tell
it
to
ignore
the
node
modules
folder
and
the
dot
get
folder,
because
I
don't
need
to
replicate
all
the
files
from
node
modules
and
get,
and
it
looks
like
I
left
off
that
particular
flag.
C
C
I
think
I
need
to
add
in
maybe
a
path
on
that
remote
system.
I
was
hoping
it
would
just
pick
up
the
working
directory
by
default,
so
I
left
it
blank
and
then
this
is
the
path
that
I
want
to
replicate,
so
I
could
potentially
try
it
again.
Let
me
do
help
r
sync
and
see
if
I
could
find
the
here
exclude.
C
Exclude
dot
get
and
I'm
not
totally
sure
about
the
syntax
if
it's
dot
get
comma
node
modules.
C
Something
like
this-
I
don't
know
anyway,
if
you're
super
interested
in
seeing
this
particular
workflow
me
try
for
a
longer
period
of
time
on
this
particular
workflow.
Let
us
know
in
chat
I'll
jump
back
on
this
and
try
to
explore
the
details
of
this
oc
rsync
command,
but
this
is
how
you
would
solve
this
using
oc.
C
There's
a
simpler
way
to
get
at
this.
If
you're
using
odo,
to
create
your
components,
you
can
run
odo
watch.
I
haven't
used
odo
yet
on
this
project.
So
odo
may
not
know
where
to
replicate
this
out
to.
But
if
I
had
odo
installed,
I
could
do.
Yeah
doesn't
have
a
component
context
because
I
haven't
started
with
odo,
but
if
I
had
started
with
odo,
initially
I'd
be
able
to
run
odo
watch
and
that
would
get
the
right
rsync
between
this
local
environment
and
the
hosted
container.
B
Yeah
yeah,
that
that
is
cool
because
it's
automatically
updating
it.
So
otherwise
you
should
need
to
or
use
air
sync
or
start
the
build
from
local.
There
oc
start
build
from
there
and
you
and
you
use
the
local
deer,
but
that
that
is
better.
You
know
it's!
It's
automatically
yeah.
C
Yeah
yeah
we
saw
how
long
that
first
build
took
a
extra
long
time
this
sandbox
might
have
had
may
have
needed
to
pull
down
images
from
the
local
openshift
registry
and
download
several
hundred
megs
of
a
base
image
onto
a
node.
Perhaps
in
order
to
do
the
build,
there's
other
things
that,
like
it
may
take
extra
time
on
the
first
build,
but
there's
definitely
some
delay
in
running
a
full
containerized
build
and
being
able
to
see
your
changes
reflected
immediately
is
a
huge
amount
of
productivity
boost.
I
think
there's
also.
C
I
wonder
if
this
button
works.
Let's
see
I
clicked
on
the
che
link
said.
C
So
there's
no
dev
file
currently
in
this
repo,
so
we'll
see
how
it
responds
to
this.
If
I
had
started
with
odo
that
would
have
given
me
a
dev
file
that
I
could
have
committed
to
the
repo.
So
that's
something
I
could
do
if
this
code
ready
workspace
has
failed.
C
I
can
pretty
quickly
whip
together,
run
together.
Some
kind
of
odo
commands
that'll
give
us
a
local
dev
file.
I
can
commit
that
push
that
and
then
we
can
try
starting
up
eclipse,
j
again
or
code
ready
workspaces,
nice.
B
I
think
this
is
gonna,
allow
the
default
workspace
when
it
doesn't
find
the
dev
file.
It's
gonna
load
a
default
workspace
with
a
git
plug-in
where,
where
you
can
clone
your
call,
you
have
a
terminal.
Maybe
there
is
an
npm
or
the
stuff
that
we
need,
but
you
can
activate
afterwards.
B
C
B
That
that
is
the
trick
when
you
use
source
to
image
the
annotation
are
automatically
added
to
the
deployment.
So
that's
in
this
in
this
way,
openshift
recognize
you
you,
you
have
some
open
code,
ready,
workspaces,
installation
there,
and-
and
this
is
how
it
works.
If
you
see
there
is
this
app
openshift,
io,
ref
and
vca
s
uri
so
reading
this
annotation
of
a
shift
understand.
There
is
some
source
code.
If
you
don't
have
quadratic
workspaces,
you
have
a
little
github
icon.
B
C
Yeah
this
was
natalie
actually
gave
me
some
of
these
annotations
to
try.
I
think,
a
couple
weeks
ago
on
the
show
we
were
trying
to
get
code
ready
workspaces
to
appear
on
a
application
that
we
installed
and
we
went
and
installed
the
operator,
but
we
only
gave
it
about
five
minutes
of
of
install
time.
We
didn't
have
enough
time
left
in
the
show
to
watch
it
all
the
way
through,
but
yeah.
This
one
was
code.
Ready.
C
B
D
C
All
right,
so
we
found
a
maybe
a
limitation
in
code
ready
workspaces.
C
Also,
another
kind
of
quirk
of
this
particular
project
is
that
we're
really
trying
to
operate
under
a
subdirectory
for
this
react
project
folder
and
some
folks
are
going
to
organize
their
applications.
This
way
and
have
kind
of
a
mono
repo
approach
with
multiple
micro
services
hosted
under
a
shared
repo.
C
That's
definitely
a
a
way
of
operating
that
a
large
number
of
companies
have
used.
So
it's
something
we
should
be
able
to
to
do
effectively.
I'm
curious
to
see
if
we
had
started
with
a
dev
file
if,
if
that
sub
path
would
would
be
easy
to
set
or
easy
to
detect
using
odo.
So
I'll
need
to
go
back
through
that
that
workflow
with
this
repo
and
see
how
that
works
out,
but
we
should
be
able
to
edit
some
of
the
code,
ready,
environment
or
basically
load
up.
C
B
C
B
Git
clone
link
under
new,
so
here
we
should
be
able
to
to
give
the
url
and
we
should
be
able
to
give
to
to
specify
the
branch.
Let's
check
if
it
asks
us
about
the
branch
in
some
way.
Maybe
I
think.
B
C
Okay,
well,
it's
nice
that
we're
yeah
we
or
did
find
a
way
just
run
git
clone
paste
in
the
the
and-
and
here
I
am
with
access
to
edit
these
files.
I
could
jump
into
the
it
should
be,
or
was
it
I'm
not
going
to
edit
the
index.html
again,
but
anyway
should
be
underneath.
It
was
in
react,
public.
C
Yeah,
so
this
should
give
me
a
nice
with
syntax
highlighting
and
everything
vs
code
plug-in
support,
all
the
nice
advanced
features,
and
probably
some
autosave
going
through,
but
this
isn't,
I
think,
synced
so
far
since
we
just
did
the
git
clone.
I
don't
think
it's
syncing
with
the
hosted
environment
here.
B
C
B
C
B
C
Okay,
nice,
all
right
so
open
shift.
Connector
is
an
another
feature
that
you
might
want
to
add
on
to
get
that
live
reload
feature
if
you're
doing
front
end
languages
that
have
this
hot
reloading
live
reloading
kind
of
support.
That's
nice!
Then
you
get
your
editor
and
everything
else,
all
bundled
up
and
ready
to
go
and
if
you're,
using
dev
files,
this
ought
to
be
a
lot
easier
to
reproduce.
C
C
Let's
see
so
next
thing
I
had
on
this
list.
That
was
the
first
objective
I
had
was
established
a
containerized
development
stage.
I'm
going
to
count
that
as
ex
as
a
success,
even
though
I
didn't
fully
finish
the
the
oc
rsync
command.
I
haven't
been
watching
chat,
but
I
didn't
hear
anyone
scream
yeah.
We
really
need
to
see
ocr
sync,
so.
C
Step
we
did
update
some
settings
on
the
service
to
get
this
to
bind
to
port
3000
other
than
that
setting
the
context
directory
and
making
sure
it
was
binding
to
the
right
port.
Those
are
the
only
two
things
I
can
think
of
that
we
needed
to
modify
to
get
this
repo
working.
So
that's
pretty
good,
considering
it
was
intended
to
work
with
a
a
docker
file
right.
A
C
C
Oh,
it
looks
like
goal.
Number
two
on
here
was
sync
changes
from
a
repo
goal.
Three
was
deploy
a
build
of
the
same
repo
using
nginx
or
a
static
server,
so
I
have
not
tried
this
step
yet,
but
should
be
able
to
do
the
same
thing
going
back
to
add
and
then
from
catalog
there
you
go
and
there
there
was
a.
I
thought
there
was
something
called
like
the
static
web
server.
There's
this
there's
a
template
and
a
builder
image.
B
Yeah,
basically,
this
is
a
source
to
image,
so
nginx
or
apache
needs
some
repository
where
to
read
your
html
files.
It
works
in
this
way,
so
it
is
automatically
done
if
you
provide
any
repo
with
some
html
file
or
apache
com
or
an
ngx
comp.
This
is
how
it
works.
A
C
B
Yeah,
it
works
from
here.
It
doesn't
work
from
ready
workspaces
because
I
think
it's
hardcoded
master
somewhere.
A
B
D
D
D
B
B
C
C
C
Might
have
to
use
dockerfile.rootless,
though
I'm
not
sure
if
we'll
be
able
to
do
that
through
the
ui,
but
we
can,
let's
see
oh
here
we
go
yeah.
C
Hopefully
that
knows
to
try,
but
hopefully
I
don't
need
to
add
this
contextur
here
as
well.
It
should
I'm
assuming
it'll,
keep
the
context
for
this.
It's
relative
to
the
context
or
field
is
what
it
says
right
there.
So
that's
cool
it'll
work,
all
right
and
let's
see,
if
is
there
a?
I
don't
see
any
port.
C
That
is
what
we
had,
I
think,
is
the
default
here.
B
C
That
sounds
like
it
matches
up.
I
was
just
checking
to
see
if
there
was
a
port
line
in
the
docker
file.
Okay,
application
front
end
I'll
call
this
run
in
docker,
run
it
as
a
deployment
and
create
a
route.
Let's
see
how
this
does
try
this
one
on.
D
B
Yeah,
you
could
do
two
builder
to
to
build
and
then
use
first,
two
image
to
the
other
build
you
did,
but
with
a
multi-stage
I
think
it's
easier.
It
should
be
fine.
This
way.
C
Not
don't.
B
Have
an
operator
yet
but
they're
they're
coming.
C
C
What
it
does
for
builds,
but
I
thought
package.json
was
running
a
react
scripts
build
so
that
should
produce.
I
wonder
if
that
exports
a
whole
dist
folder
or
if
we
kind
of
look
into
our
full
container
here
and
see
what
happened.
D
C
So
maybe
we
just
need
to,
but
there's
nothing
in
static,
no.
C
Yeah,
okay,
but
that's
just
a
subfolder,
so
maybe
I
could
just
deploy.
I
wonder
if
I
could
deploy
this
in
a
redeployed,
another
copy
of
this
image
in
a
kind
of
production
config.
C
So
we
already
have
we
have
the
files
in
a
container
in
the
system.
I
don't
know
how
to
tell
nginx
to
point
to
this
container
or
use
this.
C
Though
yeah
looks
like
this
isn't
working
out,
bummer
build
failed.
C
Oh,
is
that
the
rate
limiter
publisher-
oh
boy,
interesting,
failed
to
pull
from
docker
hub.
I'm
going
to
blame
I'm
going
to
blind
blame
docker
on
this
one.
D
Well,
it
might
be
the
rate
limit
that
I
cause,
because
what
happens
here
is
that
docker
hub
has
a
limit
of
100
image
pools
per
per
hour
by
anonymous
users
and
all
the
users
of
the
developer.
Sandbox
are
all
going
against
that
same
rate
limit
right.
All
the
users
are
using
the
anonymous
anonymous
customer.
D
A
D
The
what
you
can
do
and
there's
a
blog
post
that
was
published
like
two
days
ago
about
that
and
I'll
just.
B
D
And
paste
it
in,
but
basically
what
you
can
do
is
that
you'll
just
use
a
some
some,
your
docker
credentials
in
order
to
not
count
against
the
anonymous
user
anymore,
but
against
your
authenticated
user.
And
then
you
have
access
to
200
pulls
per
per
hour
or
something
which
you
know,
you're,
probably
never
going
to
hit
that
point.
So.
B
C
But
yeah
next
step,
I
wanted
to
do-
was
basically
package
that
up
as
a
static,
so
we
have
the
the
node.js
build
process.
We
did
built
this
for
a
production
environment.
We
ended
up
with
the
the
correct
kind
of
sub
path
and
we
can
view
it
all.
In
yeah
we
should
be
able
to
to
serve
that
up
as
well
another
kind
of
modification
you
could
potentially
make
on
your
containerized
environment.
There's
a
so
there's
the
script.
To
start
this
started
it
started.
This
react
scripts
line.
C
You
could
theoretically
use
node.js
as
a
web
server
as
well
and
have
the
default
start,
be
a
kind
of
production
mode
node.js
with
some
really
light
static,
server.
There's
a
couple
static
servers
for
node.js
they're,
pretty
easy
to
use
that
could
be
an
optional
start
value,
and
then
you
can
have
this.
One
do
have
an
alternate.
Like
start
react.
Server
could
be
the
alternate
keyword
that
you
could
use
here.
C
I
had
a
way
of
configuring:
the
source
to
image
environments,
I'm
not
a
hundred
percent.
This
is
included
in
the
in
the
latest
images,
but
there
was
a
option
you
can.
You
can
do.
Let's
see
if
I'll
pop
open
a
terminal,
you
used
to
be
able
to
set
an
environment
key
of
npm
run,
and
this
would
be
defaulted
to
to
start.
C
Actually,
let
me
let
me
see,
I
wonder
if
that's
in
the
see,
if
we
end
up
anything,
yeah
okay,
so
it's
already
set,
we
have
npm
run,
is
currently
set
to
start.
We
can
include
an
environment
key,
and
so
you
could
do
something
like
export.
C
Npm
run
equals
production
you're
better
off
using
the
start
flag,
but
you
could
have
another
one.
That's
like
dev
mode,
I
don't
know
whatever
you
could
you
can
set.
This
npm
run
key
to
whatever
value
you
want
within
the
package.json
and
then
when
we
init
your
application
using
the
node.js
image
we'll
run
instead
of
instead
of
running
where's.
My
keyboard
instead
of
running.
C
Npm
start
what
we
actually
run
is
we
run
npm
run
start,
but
you
could
do
npm
run
dev
mode
or
something
else
that's
defined
in
your
package.json
in
order
to
boot
into
kind
of
any
other
start
script.
Does
that
make
sense,
hopefully
for
folks
that
are
node.js
users?
That
makes
sense.
D
C
Yeah,
it
doesn't
get
you
a
nginx
front
end,
and
that
was
part
of
what
I
was
trying
to
accomplish
in
this
session,
but
it
would
give
you
the
ability
to
set
up
this
whole
workflow
using
sandbox
and
what's
existing
in
sandbox.
Today,
you
just
overload
the
package.json
scripts
and
then
export
something
that's
npm
run
and
whatever
script
you
want
to
run
and
it'll
boot
into
that
mode.
C
So
that
is
we're
running
out
of
time
for
this
session,
but
hopefully
a
solid
introduction
to
front-end
containers
using
joel's
new
front-end
containers
repo.
There
are
other
examples:
angular
vanilla,
which
I
assume
is
kind
of
like
a
minimal
version-
is
that
right.
C
Nice,
nice
there's
a
there's,
a
core
built-in
module
in
node.js
called,
and
I
remember
there
was
a
framework
a
long
time
ago
where
someone
was
saying:
http
is
a
framework
just
use
the
built-in.
That's
that's
your
framework,
so
yeah,
it's
nice
to
have
a
super
minimalist
implementation,
as
opposed
to
a
big
thick.
One
like
like
react,
which
is
pretty
thick
as
far
as
front
ends,
go
view
also
another
cool
option,
I'm
interested
in
trying
out
in
here
so
hopefully
we'll
have
a
more
javascript
examples
in
the
future.
C
Let
us
know
in
chat
or
in
that,
via
that
feedback
form,
if
you
have
other
frameworks
or
technologies
that
you're
interested
in
seeing
on
the
open
shift
office
hours
yeah,
let.
A
Me
grab
that
dev
feedback
link.
Please
fill
that
out
and
let
us
know
what
you
want
to
see
here
on
the
channel
and
definitely
definitely
subscribe
to
our
calendar.
So
you
know
when
that
thing
you
requested
is
going
to
be
coming
up.
That
is
all
the
streaming
we
have
for
today.
Folks,
some
people
are
on
pto.
My
team
is
on
apac
time
right
now
visiting
all
of
our
customers
over
there,
virtually
but
still
in
their
time
zone.
So
there's
a
lot
of
more
fun
stuff
this
week.
A
So
you
know
tomorrow
we're
not
going
to
have
the
level
up
hour
as
a
result
of
my
team
being
in
apac,
but
we
still
have
the
the
open
shift,
administrator
office
hours
and
red
hat
and
enterprises
links
presents
tomorrow
on
the
channel,
so
yeah
we're
also
working
on
some
new
shows
so
stay
tuned.
Folks,
as
always,
we
are
super
busy.
Yes,
jill
mentioned
his
twitter
handle
joel
lord,
with
two
underscores
in
between
the
two
words.
I
am
chris
short
all
one
word
natalie.
You
are
bluesman84.
A
Automation
there
you
go
and
there
is
ryan
j
on
twitter
as
well,
so
feel
free
to
reach
out
to
any
of
us.
You
have
any
questions
concerns
you
know.
Feedback
comments
want
for
content,
whatever
you
need
we're
here
to
help
you
all
and
anything
content
related,
feel
free
to
email
to
me
see
short
redhead.com.