►
From YouTube: OpenShift Online 3 Developer Preview Walkthrough
Description
In this video, Grant Shipley shows you the new OpenShift Online 3 Developer Preview environment and how to get started quickly using the platform.
Around 42:33 the correct command is:
oc env dc/grantpphp -e MYSQL_USER=grantmysql
A
Hey
everybody,
this
is
grant
your
friendly
openshift
team
member
over
at
Red
Hat
and
today,
I
want
to
show
you
how
to
use
the
new
OpenShift
online
developer
preview
running
the
latest
and
greatest
version
of
our
code.
If
you're
not
familiar
with
what
we've
been
working
on
over
the
last
year
or
so,
we
have
integrated
native
docker
containers
and
orchestration
with
the
kubernetes
system
to
the
platform.
So
now
you
can
interact
with
the
platform
using
docker
and
orchestrate
everything
with
kubernetes.
So
hopefully
you
have
an
account
for
the
developer
preview
version
of
OpenShift.
A
A
Walkthrough
now
I'm
doing
this,
not
scripted
so
I
just
wanted
to
take
a
few
minutes
today
and
show
you
guys
how
to
use
it
once
you
get
your
account,
because
it
is
a
dramatic
departure
from
what
you're
used
to
with
OpenShift
online,
and
we
have
millions
of
applications
deployed
out
to
version
2
of
OpenShift
online,
which
you
can
get
to
just
going
to
open
shift
comm,
and
so,
as
you
begin
to
think
about
migrating,
your
applications
over
to
our
new
system
watch.
This
video
don't
give
you
some
tips
and
tricks.
A
So
the
first
thing
I
want
to
do
is
just
log
in
to
the
developer
preview
console
so
to
do
that,
I'm
going
to
go
to
preview,
dot,
OpenShift
comm
and
throw
in
console
at
the
beginning
here
just
in
case
it
doesn't
redirect
me.
The
first
thing
you're
going
to
notice
is
that
we
allow
you
to
off
with
github.
That's
pretty
crazy,
cool
right
and
you
can
see
it's
openshift
online
developer
preview
and
if
you
are
like
most
people,
you've
been
waiting
for
a
couple
years
on
this.
A
So
you're
probably
pretty
excited
now
that
we
have
this
out
to
where
you
can
start
looking
at
so
I'm
gonna
go
ahead
and
login
with
github.
Here
it's
gonna
ask
me
to
off
put
in
my
github
username
my
password
and
I'm
typing
in
real-time
here
and
I.
Do
have
a
mechanical
keyboard,
so
I
apologize
if
the
keys
are
a
little
noisy,
but
that's
how
you
know
that
I'm
actually
doing
this
in
real-time.
A
So
the
first
thing
that
you're
going
to
be
pleased
to
see
is
this
is
indeed
OpenShift
online
and
I
don't
have
any
projects
yet
so
the
difference
between
OpenShift
online
version
2
in
this
new
platform
is
the
in
version
2,
which
you're
all
familiar
with.
We
had
these
concepts
of
domains
or
namespaces,
and
now
we
group
everything
with
a
project.
So
it's
just
a
nice
organizational
feature
to
allow
you
to
group
things
together.
A
You
give
a
description
if
you
want
to
I'm
just
gonna,
say
a
description
and
click
on
create,
and
so
now
I
have
a
new
project
created,
and
the
first
thing
it
wants
to
do
is
ask
me
to
create
a
new
application,
but
before
we
do
that,
I'm
going
to
show
you
just
a
few
other
things,
real
quick.
If
I
click
back
on
openshift
online
here
I
can
go
back
to
a
project
overview
page
to
where
I
can
view
all
of
my
projects.
We
can
see
the
one
I
just
created
and
delete
this
project
from
here.
A
I
can
create
another
new
project:
you're
not
going
to
have
access
to
create
a
new
project
other
than
one
and
the
developer
preview
based
on
quota
a
couple
other
things
I
want
to
show
you
if
you
click
on
this
question,
mark
right
here.
If
you
click
on
a
bout,
this
is
where
you
can
verify
the
versions
that
we're
running
an
open
chef
version,
three
two
and
we're
running
kubernetes
version
wants
you.
This
is
also
important
because
it
links
to
the
appropriate
command-line
tool
for
your
operating
system.
A
Now,
a
lot
of
people
like
to
use
the
command
line,
that's
what
I
prefer
using,
but
I'm
going
to
show
you
a
mix
of
both,
and
so,
if
you
do
want
to
use
the
command
line
tool
or
the
CLI
just
download
the
correct
one
here
now.
This
is
a
lot
easier
than
openshift
online
version
two,
because
we
have
switched
over
to
use
the
go
programming
language
and
we
provide
a
single
executable
for
each
operating
system.
A
So
we
no
longer
have
the
dependency
on
Ruby
and
and
SSH,
and
all
this
other
stuff
that
you
had
to
have
installed
before.
So
you
can
just
download
this
single
executable.
Add
it
to
your
path
and
you're
done
and
then
how
you
authenticate
is
a
little
bit
different
in
open
chip,
3
everything's
token-based.
Remember
we
authenticated
with
github.
So
how
do
you
actually
authenticate
to
the
platform
and
if
you
want
to
connect
it
via
a
command
line
tool,
you
can
see
that
it's
down
here
you
can
just
copy
and
paste
this.
A
A
So
let's
go
back
to
our
platform
here
our
platform
overview
and
go
into
my
project
on
container
application
project,
and
it's
this
is
an
empty
project
right
now,
so
let's
go
ahead
and
add
something
to
it
now,
just
for
simplicity,
sake,
I'm,
going
to
add
a
PHP
application.
The
process
is
the
same
regardless.
If
you
want
to
use
Java
Ruby
Python
Perl,
whatever
the
case
may
be
okay.
A
So,
let's
go
ahead
and
click
on
add
to
project,
and
this
is
where
I
can
select
any
existing
docker
images
or
builder
images,
that
is
in
the
openshift
registry,
the
openshift
docker
registry,
that's
part
of
the
platform,
and
so,
if
I
come
down
here
to
PHP
I
see
we
have
a
couple
of
PHP
images.
We
have
5
5
5
6,
we
have
the
latest.
We
also
have
some
samples
you
can
also
filter
by
keyword
if
you
just
want
to
show
all
the
PHP
ones
now.
A
On
line
three,
we've
created
a
new
project
called
source
to
image,
and
this
is
going
to
simplify
your
life
as
a
developer.
So
much
you're
gonna
absolutely
love
it.
So
let
me
show
you
how
that
works.
I'm
gonna
use
PHP
five
six
here
and
it's
asking
me
for
a
name
and
I'm
going
to
just
call
this
grant
PHP
and
check
this
out
right
here.
It's
asking
for
a
git
repository,
URL,
so
OpenShift
on
line
three
much
like
the
previous
version
prefers
git
as
the
source
code
management
system
to
interact
with
the
platform.
A
A
Have
this
simple
PHP
application
that
I
modified
26
days
ago
and
I'm
going
to
just
get
the
get
URL
for
this
I'm
gonna
copy
that
pop
back
over
to
my
openshift
console
here
and
I'm,
going
to
paste
that
in
okay
and
I'm
gonna
click
on
create
and
bam.
That's
all
there
is
to
it
so
now
under
the
covers.
What
openshift
on
line
3
is
doing
is
it's
cloning
that
source
code
repository
and
it
is
making
a
new
docker
image
on
the
fly
that
matches
what
you
need
for
your
application
to
run.
A
So
it's
taking
that
PHP
5
6
base
image,
that's
actually
running
on
top
of
Red
Hat
Enterprise
Linux,
and
it's
going
to
build
your
source
code.
If
it
needs
to
be
built,
it's
going
to
resolve
any
dependencies
if
you
have
any
composer
dependencies
or
maven
dependencies
or
package.json
dependencies.
Whatever
the
case
may
be,
it's
going
to
get
this
application
into
a
deployable
artifact.
It's
then
going
to
layer
that,
on
top
of
the
base,
docker
image
and
create
a
new
one
on
the
fly
for
you
and
then
deploy
that
out.
A
A
Inside
of
the
build
we
can
see,
the
status
is
the
surrounding
that
was
started
a
minute
ago.
It's
been
running
for
one
minute
36
seconds
now.
This
does
take
a
little
bit
of
time.
The
first
time
you
create
this
image
and
will
see
some
subsequent
builds
are
going
to
be
much
faster.
You
can
see
where
it's
putting
the
image
inside
of
the
docker
registry
and
here's
the
URL
for
that
the
source
type
is
get
the
source
repo
I
pulled
from
the
master
branch.
You
can
pull
from
any
branch
you
want.
A
My
output
image
is
called
on
cap
grant
PHP.
That
is
my
outputted
docker
image
and
here's
my
push
secret
that
we
needed.
No,
my
build
actually
finished
now.
If
we
go
over
to
the
environment,
if
we
had
any
environment
variables,
we
could
see
that
logs
I
showed
you
events.
You
can
kind
of
get
a
feel
for.
What's
going
on
at
one
twenty
two
in
the
afternoon,
I
assigned
a
build
and
you
can
go
through
and
follow
the
process
here.
A
It
created
the
image
it
started,
they
can
or
started
to
contain,
and
then
it
created
container
okay.
So
let's
go
back
to
our
overview
and
sure
enough.
Now
my
application
is
running,
and
here
is
the
application
overview
piece
of
the
web
console
so
I
have
a
service
called
grant.
Php
that
was
created
now.
Go
into
all
of
this
in
more
detail
in
just
a
second
here
is
the
actual
URL
for
my
application.
A
It
created
that
default
route
as
it
deployed
this
out
via
that
service
that
was
defined,
so
I'm
not
go
ahead
and
click
on
that.
That's
probably
what
you
want
to
see,
and
you
can
see.
This
is
just
a
little
message.
I
was
testing
something
earlier,
so
it's
gonna
say
this
is
a
change
from
Orion.
I
was
actually
looking
at
the
Orion
IDE,
pretty
cool,
but
we'll
get
into
that
in
another
video,
and
we
have
my
builds
completed.
A
I
can
view
the
log
I
can
dismiss
the
build,
and
right
here
is
my
running
application
running
inside
of
the
docker
container.
That's
actually
encapsulated
inside
of
a
kubernetes
pod.
We
can
see
the
image
that
it's
using
with
the
hash.
How
big
that
image
is?
It
turned
out
to
be
a
hundred
and
seventy-five
Meg's
the
build
that
that
is
currently
deployed
the
source
and
the
ports.
That's
listening
on.
Ok!
So
the
first
thing
I
want
to
show
you
is
how
to
scale
this
bad
boy
up
to
scale
up
a
application
in
OpenShift
on
line
3.
A
All
you
do
is
you
click
simply
click
the
scale-up
button
and
it's
going
to
quickly
scale
that
up
to
2
pods,
add
it
to
the
service
and
then
begin
to
load
balancing
so
now,
I
have
2
of
these
running
and
if
we
click
on
this
sure
enough,
the
app
is
still
responsive.
You
can
scale
back
down
to
1
if
you
no
longer
need
that
traffic,
and
so
the
scaling
is
very
responsive
inside
of
openshift
on
line
3,
it's
almost
instantaneous,
it's
so
quick.
A
It's
phenomenal
now,
even
if
you're,
using
Java
with
a
JBoss,
Enterprise,
Application,
Platform
server
or
a
tomcat
server,
the
scaling
is
just
as
quick,
even
in
the
other
programming
languages,
because
again
it's
just
scaling
a
container
that
it's
already
built
and
adding
another
one.
So
let's
start
diving
in
here
and
see
some
of
the
features
of
and
shift
on
line
three
now
that
we
have
a
simple
application
deployed
and
are
able
to
use
it.
A
The
first
thing
I
want
to
show
you
is
kind
of
a
manager's
dashboard,
orchestration,
View
tool,
I,
don't
know
I'm
a
I'm,
a
developer
at
heart,
so
I
don't
really
use
it
that
much,
but
you
can
see
that
it
shows
your
entire
application
inside
of
a
nice
little
view
here.
So
you
can
see
you
know
what's
going
where
and
how
things
are
interconnected,
and
this
is
the
entry
point
and
we
have
the
running
application.
You
can
click
on
it
and
things
will
update
over
here.
Here's
my
pod,
if
I
click
on
this
orange
thing.
A
This
is
my
service
and
this
is
my
route.
So
the
entry
point
comes
in
through
the
route
to
the
service
to
the
pod
back
to
the
replication
controller
and
then
a
deployment
configures
hunk
off
of
that
as
well.
So
let
me
move
the
pod
up
here
and,
let's
just
go
back
to
the
overview
and
scale
scale
up.
Oops
click
the
wrong
button.
Let
me
scale
this
up
to
two
and
once
we
have
the
second
pod
running
here.
A
I'll
show
you
that
tool
again,
and
you
can
see
that
now
we
have
two
pods,
that's
actually
serviced
via
the
route.
Okay.
So
let
me
drag
a
few
things
around
here.
I'll
show
you
how
this
is
working
okay,
so
we
have
external
requests
coming
in
through
the
route
it's
going
to
hit
the
service,
which
is
the
load
balancer,
that
load
balancers.
This
is
going
to
serve
the
route
or
the
traffic
to
one
of
these
two
pods.
A
This
pod
is
backed
by
a
replication
controller
and
a
deployment
config,
which
defines
what
the
application
state
should
look
like,
make
sense,
okay,
cool!
So
let's
go
back
over
here,
we'll
scale
back
down.
We
don't
actually
need
two
of
these
pods
running
and
I
want
to
go
into
browse
and
show
you
a
few
of
the
features
and
different
things
you
can
look
at
under
browse.
You
can
look
at
builds.
We
already
looked
at
the
build
as
it
was
happening,
but
I
can
come
in
here
on
the
build
look
at
the
logs.
A
I
can
also
start
a
new
build
if
I
want
I'll.
Just
you
know,
click
on
start
build
and
that's
going
to
follow
that
same
procedure
that
it
did.
Initially
it's
going
to
check
for
changes
in
that
upstream
git
repository,
it's
going
to
build
a
new
image
and
deploy
that
out.
You
can
also
edit
the
gamal
for
the
build
directly
inside
of
the
browser.
If
you
want
to
get
down
into
the
nitty-gritty
details
of
how
the
build
works,
maybe
you
want
a
different
strategy.
A
Whatever
the
case
may
be
it's
beyond
the
scope
of
this
introductory
video,
but
you
can
edit.
This
ya
know
file
directly
inside
the
browser.
Now,
do
you
remember
when
I
told
you
that
the
first
time
takes
a
little
bit
longer?
I
just
want
to.
You
know,
prove
to
you
because
I
know,
you
don't
believe
me,
but
I
was
doing
it
in
real
time.
Here
you
can
see
the
first
bill
took
1
minute
56
seconds
and
the
second
build
like
I
promised,
was
much
faster.
It
took
22
seconds.
A
Ok
and
oh,
we
almost
missed
it,
but
you
could
have
seen
the
rolling
deployment
so
we'll
come
back
and
do
that
again
in
a
little
bit.
So
if
I
click
on
deployments,
I
have
actually
done
two
deployments.
That
makes
sense
right
because
I
did
two
builds
and
so
I
had
to
specific
deployments,
and
so
I
can
go
in
to
this
deployment
and
actually
look
at
some
of
the
details
on
this
and
you
can
modify
some
of
these
things.
You
can
look
at
the
timeout
parameters
you
can
set
selectors.
You
can
see
what
image
is
deployed.
A
What
the
latest
source
code
is
that's
been
deployed.
It
also
gives
you
some
help
if
you
want
to
manually
deploy
from
the
command
line
now
down
here.
If
you
can
see
that
it's
deployed
one
req
replica
of
our
latest
build
it
was
created
a
minute
ago
and
it's
gonna
trigger
on
an
image
change.
The
only
time
that
image
changes,
it's
gonna
make
a
new
rolling
deployment.
Also,
at
this
point,
you
can
attach
persistent
storage
to
your
container.
That's
friggin
awesome
right.
A
So
if
you
click
on
attach
persistent
storage,
I
don't
have
any
persistent
volume
claims
I
would
have
to
add
one
of
those
first,
but
I
can
actually
attach
persistent
storage
to
my
running
pod,
and
if
that
pot
goes
down
and
comes
back
up,
the
storage
will
still
be
there.
Why
is
that
important?
That's
important
in
case
you
want
to
I,
don't
know,
save
your
data
in
the
database
that
we're
gonna
in
a
few
minutes,
so
any
stateful
application
you
want
to
run
on
the
platform.
A
A
You
know
we
keep
the
users
requests
and
in
mind
as
we're
developing
this
new
stuff,
instead
of
trying
to
force
everyone
down
a
brand
new
paradigm.
So
enough
of
a
tangent
on
that,
let's
go
back
to
our
browse
and
look
at
events.
This
is
the
full
event
stream
or
event
log
from
everything
that
I've
been
doing
today
we
can
see
we
just
started
a
container
right
here.
You
can
filter
by
time
name,
severity,
reason
all
kinds
of
cool
stuff.
You
can
look
at
there
we're
now
going
to
take
a
look
at
pods.
A
A
So
you
can
actually
look
at
these
pods
now
they're
no
longer
running
as
you
can
see
here,
the
containers
ready
is
zero
out
of
one
on
this
build
too,
but
our
actual
application
is
running
inside
of
this
pod
right
here,
and
so,
if
I
click
on
that,
we
can
see
that
it
is
indeed
running.
Here's
the
IP
address.
Here's
the
note
that
it's
running
on,
which
is
pretty
handy.
If
you
ever
need
that
information,
here's
the
state
and
here's
the
template
that
it
used
just
some
more
information
about
it.
A
You
can
see
how
much
memory
it's
using
its
using
307
and
a
512
the
auth
token.
You
look
at
environment
variables
which
I
haven't
configured
any
yet
you
can
look
at
the
pot
or
the
logs
on
the
running
container
inside
of
the
web
browser
which
is
really
cool.
One
of
my
favorite
things
to
do
is
click
on
this
terminal.
Here
and
you
can
actually
look
at,
you-
know
open
up
a
terminal
session
on
your
running
container
inside
of
the
web
browser,
if
you
needed
to
you,
know
just
check
something
out
real
quick.
A
Maybe
you
want
to
look
at
the
environment
variables
without
having
to
do
it
locally
on
your
own
system,
maybe
you're
on
a
different
system,
and
you
don't
have
the
OSI
tool
installed
or
whatever
the
case
may
be.
You
can
just
pop
right
into
the
web
console
and
take
a
look
at
there,
and
then
you
can
look
at
events
just
for
the
running
pot.
Now
we'll
take
a
look
at
routes.
Routes
is
what
exposes
my
application
to
the
outside
world.
A
It's
what
created
that
URL
that's
available
if
I
click
on
that
this
is
my
application
right,
and
so
you
can
modify
this
or
change
it.
If
you
come
in
here,
you
can
edit
the
gamal.
You
know
change
the
hose
to
whatever
and
create
different
routes.
Alright,
let's
go
back
to
browse
services.
This
is
the
you
can
think
of
this
as
the
load
balancer.
It's
kind
of
the
entry
point
into
the
application
and
you
can
click
down
and
get
more
details
on
that
as
well.
A
Look
at
a
fence
and
then,
lastly,
you
can
click
on
storage,
and
you
can
see
that
I
don't
have
any
persistent
volumes
to
actually
claim
right
now,
but
this
is
how
you
would
attach
stuff.
Okay,
let's
go
down
to
settings
real,
quick
and
discuss
a
little
bit
about
quota
on
open
shift
on
line
3.
Now
everyone
knows
open
shift
online.
A
The
public
version
of
the
open
shift
cloud
that
we
offer
has
been
free
of
charge
for
people
to
use
and
that's
been
phenomenal
for
people
and
for
developers
to
try
things
out
a
very
low
barrier
to
entry,
and
we
are
happy
to
announce
that
we've
included
that
with
openshift
on
line
three
as
well
in
openshift,
on
line
two
you're
able
to
create
up
to
three
containers
each
with
512
Meg's
of
RAM.
And
so
let's
look
at
what
the
developer
preview
has
four
limits.
A
Right
now
for
CPU
and
memory
you
get
up
to
2
gigabytes
of
memory
to
use
and
you
can
specify
when
you
create
a
container
or
application.
How
much
you
want
to
actually
use
and
then
based
on
the
amount
of
memory
that
you
allocate
to
a
container,
is
how
much
CPU
you
actually
get.
I
hope
that
makes
sense,
but
you
can
come
in
here
and
you
can
look
at
how
you're
actually
using
things,
but
the
restriction
or
the
quota
before
the
Developer
Preview
is
based
on
the
memory
which
is
set
at
note.
A
This
is
saying
1.3
and
up
here
at
San
2,
so
I
have
to
dig
into
that
and
see
which
one
it
actually
is,
and
then
you
can
look
at
how
much
memory
and
CPU
you're
actually
using
at
any
point
in
time.
Ok,
so
let's
go
back
to
our
overview
here
and
let's
actually
scale
this
down
to
0
pods.
We
don't
actually
want
it
anymore,
but
that'll
leave
it
running.
Let's
say
I
want
to
do
some
maintenance
on
the
application,
and
you
know
I
didn't
want
it
to
be
up
while
I
was
doing
it.
A
I
can
just
scale
it
down
to
0
pods
when
I'm
ready
to
start
serving
the
application
again.
I
can
just
scale
it
back
up
to
1,
pod
and
it'll
start
handling.
Those
requests
again,
ok,
so
let's
take
a
look
at
adding
the
database.
So
if
I
click
on
add
the
project-
and,
let's
say
I
want
to
add
my
SQL
here-
here's
a
MySQL
persistent-
maybe
we
want
to
do-
let's
see
if
we
have
in
here
we
have
MongoDB,
should
probably
have
Postgres
as
well.
Yep
sure
enough.
A
A
This
is
where
you
can
specify
how
much
disk
space
you
want
your
application
database
to
actually
be
able
to
use
so
I'm
gonna
click
on
create,
and
if
we
go
back
over,
we
can
see
that
this
is
going
to
start
spinning
this
out.
Okay,
so
while
that's
running,
let
me
show
you
how
to
make
a
code
change
to
your
application.
So
if
I
go
into
my
PHP
application
and
if
I
look
at
the
builds
here,
we
can
see.
A
Let
me
look
at
built
number
two,
that
this
is
coming
from
my
source,
repo
of
G
Shipley,
dot,
simple
PHP.
Let
me
pop
that
open
in
a
browser
again
and
let
me
copy
this-
the
URL
to
clone
clone
the
repo
all
right.
So
I'm
gonna
go
to
my
command
line
here
and
let
me
clear
this
and
I
am
just
going
to
run.
I
get
clone
and
clone
that
repo
down
so
now,
I
have
it
okay
and
so
I'm
gonna
go
into
simple
PHP
and
I'm
gonna.
A
A
So
let's
do
that
first
and
you
can
see,
I
may
not
have
get
configured
yet
for
this
particular
environment.
Okay,
so
our
source
code
has
been
pushed
up
to
github.
So
now
let
me
switch
back
over
to
our
project
and,
if
I
click
on
the
route,
you
can
see
that
it's
still
the
old
one
that
I
had
in
here.
So
how
do
we
actually
deploy
this
new
version
now?
The
way
you
do
this?
Is
you
go
into
your
build?
A
Just
click
on
that
button,
click
on
start
build
and
that
is
going
to
pull
down
the
most
recent
source
code
from
github
and
it's
going
to
create
a
new
docker
image
on
the
fly
and
it's
going
to
deploy
that
out.
So
I
want
to
watch
this
page
right
here.
While
it's
running
it
should
happen
fairly
quickly.
Here
now
we
have
two
things
here.
A
This
is
our
database
right
here,
and
this
is
our
PHP
application,
and
this
is
what
I
want
to
show
you
that
rolling
deployment
so
that
it
pulled
that
code
down
built
a
new
docker
container,
which
this
is
deploying
that
docker
container
it's
in
a
ready
state,
so
it
skills
the
other
one
down
and
it
removes
it
from
the
load.
Balancer
awesome
like
pal
Bob's,
your
uncle
look,
how
fancy
that
was!
That
was
pretty
cool,
and
so
now,
if
I
click
on
this
URL,
we
can
see
that
my
source
code
has
been
updated.
A
Welcome
to
openshift
online
developer
preview.
So
let
me
show
you
another
way
to
do
this.
Okay,
let's
go
into
our
build
and
let's
look
at
our
configuration
here.
So
on
my
configuration
we
support
both
generic
web
hooks
and
github
specific
web
hooks.
So
if
you're
using
git
lab
or
something
like
that,
you
can
set
a
web
hook.
So
I'm
gonna
show
the
URL
for
this
github
webhook
and
I'm
gonna
copy
that
to
my
clipboard
I'm
gonna
go
over
to
my
github
project
and
I'm
going
to
look
at
the
settings
here
and
it's
been
a
while.
A
A
Actually
you
could
probably
leave
that
on.
If
we
have
a
valid
security
certificate
which
I
assume
we
do,
but
maybe
not
I,
don't
know,
and
then
click
on
AB
web
hook.
Ok,
so
now
anytime
I
make
a
change
to
my
project.
We're
gonna
see
a
build
automatically
happen.
So,
let's,
let's
go
to
the
overview
page
and
I'm
gonna
pop
this
up
and
I'm,
going
to
make
this
command
line
just
a
little
bit
smaller
clear.
A
The
page,
maybe
I
my
index.html
file
again
here,
and
maybe
we
want
to
echo,
maybe
a
line,
break
and
say
automated
builds.
Ok
and
let's
save
that
we're
gonna
get
commit
bills,
we'll
just
give
that
we
get
push.
So
now
we
can
see.
Look
how
quick
that
was.
That
was
awesome
as
soon
as
it
got
up
to
github.
It
called
that
trigger
inside
of
OpenShift
and
it
triggered
this
new
build.
So
we
have
a
new
build
for
running
just
bite
me
pushing
my
code
over
to
open
shift.
A
Now
again,
this
is
gonna,
take
about
26
27
seconds,
which
is
pretty
phenomenally
fast
for
what
we're
actually
doing
under
the
covers,
but
hold
on
to
your
horses,
ladies
and
gentlemen,
because
I'm
gonna
show
you
even
faster
way
in
just
a
second,
so
this
build
is
gonna,
be
completed
here.
It's
doing
that
rolling
deployment
again
and
now
it's
scaled
down
to
0
removed
it
from
the
load
balancer
or
the
service
inside
of
open
shift.
And
now,
if
we
click
on
this,
we
can
see
that,
just
by
pushing
my
code,
this
was
updated,
awesome!
Okay!
A
So
how
can
we
make
this
faster?
Now,
let's
go
to
the
command
line
and
what
I
want
to
do
is
maybe
I
want
to,
let's
say,
open
up
a
new
terminal.
Now,
let's
just
look
use
this
one.
So,
let's
do
a
VI
index,
dot
PHP
and
let's
echo
even
faster
and
we're
gonna,
save
that
now,
if
I
just
want
to
copy
that
directly
into
my
container,
I
can
say:
OC
get
pods.
This
can
give
me
my
pod
ID,
which
is
right
here.
A
I
can
do
OC
our
sink
and
I'm
going
to
say
pod
and
it's
been
a
while
since
I've
done
this,
so
let
me
actually
do
a
help
here,
just
to
get
the
source
destination.
Okay,
let's
do
OCR,
sync
source
is
dot
and
the
destination
is
going
to
be
our
pod
ID,
which
is
grant
PHP
and
it's
HC
oops.
If
I
could
type
here,
HC
and
I
can't
type
for
HC,
I
still
can't
type
okay
and
then
we're
gonna
send
that
to
we
need
to
get
the
directory.
A
A
So
let's
do
is
/opt
at
root,
slash
source,
all
right
nope.
Maybe
that
didn't
work,
I,
don't
know,
let's
see,
let's
go
back
and
check
it
and
it
says
even
faster.
So
now
we
kind
of
get
our
flow
here
if
I
can
make
this
cleaner.
Let
me
echo
a
new
break
here
boom
and
we'll
save
that
and
then
our
sync
it
over
and
then
refresh
our
browser,
and
we
can
see
that
I've
updated
that
code
in
a
little
time.
Okay,
so
that
was
pretty
cool.
We
were
able
to
quickly
deploy
the
application
now
with
arcing.
A
Now
I
do
have
another
YouTube
video.
That
shows
you
how
to
configure
your
integrated
and
development
environment
to
use
the
rsync
command,
and
in
that
scenario
any
time
you
press
the
Save
button
in
your
IDE
or
save
a
file.
It's
automatically
are
synced
over
and
that's
how
you
get
instant
gratification
with
your
source
code
changes
on
OpenShift
on
line
3,
so
you
can
use
it
as
a
true
development
environment.
So
just
Google,
instant,
gratification,
OpenShift
and
you'll
see
the
video
that
I
made
as
well
as
the
blog
post.
A
While
we're
talking
about
IDE
I,
do
want
to
show
you
guys
the
IDE
integration
that
we
have
so
I'm
just
going
to
pop
open
eclipse
here
and
I'm.
Gonna
click
on
open
shift
application,
and
this
is
gonna
open.
The
Eclipse
JBoss
tools
and
I'm
gonna
select
open
shift,
3
and
my
server
since
you're
on
the
developer
preview.
A
You
can
do
console
preview,
open
shift,
calm
and
we
actually
probably
need
to
throw
a
HTTP
on
the
front
there
and
then
we're
gonna
do
with
OAuth
and
remember
we
have
a
tokens
now
so
I
can
click
on
retrieve.
That's
gonna
pop
open,
a
little
dialogue,
that's
asking
me
to
login
with
github
and
so
once
I
close
that
I
now
have
that
token
right
inside
of
there
and
it's
going
to
off
over
to
open
ship.
For
me,
here's
my
open
shift
project
on
container
application
platform.
A
I
can-
and
this
is
where
I
have
a
decision
me.
If
I
had
an
existing
project
inside
of
Eclipse
I
can
browse
to
that
project
and
deploy
that
over
to
openshift.
Otherwise,
I
can
select
to
do
like
a
JBoss
PHP
image
here
or
you
know,
PHP
five,
six,
that's
what
we
did
before
if
I
click
on
next,
it's
gonna
give
me
a
name,
my
PHP
app.
It's
gonna
ask
for
my
git
repo,
and
so
let
me
just
copy
that
over
real
quick.
Let
me
go
back
to
the
browser
and
get
the.
A
Repo
URL
for
that,
okay-
and
let
me
go
back
to
Clips
paste
that
in
and
basically
we
can
configure
a
web
hook,
build
trigger
like
we
did
in
the
web.
Ui
I
don't
actually
want
to
do
that,
click
on
next
and
next
and
setup
our
service
ports,
our
service,
what's
gonna,
listen
on
80
and
we
can
define
our
pod
to
listen
on
8080,
that's
how
the
load,
balancer
works
and
click
on
finish,
and
this
is
actually
going
to
create
a
new
application
for
me
inside
of
openshift
on
line
3
all
from
within
eclipse.
A
Firefox
browser
and
go
back
to
my
open
shift,
console
and
click
on
overview.
We
can
see
that
we
have
a
new
PHP
app
running.
This
build
was
actually
all
started
from
inside
of
Eclipse.
We
can
look
at
the
log
file
here
and
follow
it
just
like
we
did.
You
know
everything
before
it's
pushing
that
image
over,
and
so
this
is
gonna
be
deployed
in
just
a
second,
and
if
we
go
back
to
eclipse,
you
can
see
that
it
actually
clone
the
repo
for
me
and
here
it
is.
It
opened
it
in
a
different
editor.
A
Sorry
about
that
me
click
on,
cancel
there,
alright!
So
actually
let
me
go
in
here
and
just
quick.
You
quickly
show
you
this.
If
I
go
into
look
at
my
project
properties
and
click
on
builders,
instead
of
haven't
you
go
out
to
that
other
video
to
show
you
how
to
do
it
inside
of
here,
I'm
gonna
click
a
new
one,
and
we
want
to
run
a
program.
Click
OK
and
our
new
builder
is
going
to
be
called
our
sink
and
the
location
is
the
location
of
your
OC
command
line
tool.
A
So
let
me
get
that
real,
quick
I'm
just
gonna
pop
over
here
and
say
which
OC-
and
this
is
going
to
give
me
the
location
of
my
OC
command
line
tool.
So
just
use
you
know
whatever
location
you
installed
it
in,
and
my
working
directory
I
want
that
to
be
my
project,
so
I'm
gonna
click
OK.
There.
Ok,
now
my
arguments
we
want
to
pass
in
just
like
we
did
our
sink
and
then
it
was
the
current
directory
and
then
our
pod
ID.
A
So
let's
go
back
to
the
browser
again
here
and
we
can
get
the
pod
ID
here
right
there.
It
is
I'll
copy
that
and
we'll
go
back
over
to
eclipse
yet
again
paste
that
in
and
then
a
colon
and
then
it
was
opt
app
root,
slash
source
of
leave
us
what
it
was:
click
on
apply
and
click
OK,
and
let
me
just
make
sure
that
everything,
so
everything
should
be
good
here
environment.
We
need
to
go
to
build
options
and
launching
backgrounds,
and
we
want
this
to
be
rendering
auto
builds
as
well.
A
A
So
now,
if
I
edit
this
index
dot
PHP
file
and
then
close
Visual
Studio
code,
I,
don't
know
why
that
popped
up.
No
because
I
don't
have
a
PDT
installed.
So
I'm,
just
gonna
open
this
with
a
text
editor
and
we
can
say
echo
boom
and
we're
going
to
save
that,
and
we
can
see
that
it
synced
over.
My
change
go
back
to
my
overview
page
here.
Click
on
this
Oh
unexpected
in
the
file
I
screwed,
something
up.
A
So
let
me
let's
go
back
to
eclipse
it
and
fix
that
real
quick
I
forgot
my
semicolon,
so
save
that
we
can
see
the
our
sync
happening
right.
There
go
back
to
Firefox,
reload
and
boom,
so
this
is
kind
of
the
workflow
that
you
can
use.
Let
me
split
screen
this,
so
you
can
see
this
work
a
little
bit
faster
here
and
let
me
open
eclipse,
backup
it
and
resize
it.
A
This'll
be
good.
So
let's
echos
breaks
here
and
say
automated
deploys.
I
can
spell
right
here
and
we're
just
going
to
save
that
some
it's
clicking
the
Save
button.
If
I
can
find
it
here,
I'll
just
use
the
hotkey
and
come
over
here.
Click
refresh
hope,
I
hit
it
before
the
sync
happened.
We
can
see
automated
deploys.
Oh,
but
that's
still
bold.
We
don't
actually
want
bold.
Let's
turn
off
bold,
we'll
save
that
come
over
here
refresh,
so
you
can
see
that
I'm
getting
instant
gratification
with
that.
So
that's
the
Eclipse
IDE
and
integration.
A
It's
super
awesome,
especially
if
your
IDE
person
in
the
Java
world,
you
can
do
everything
right
from
inside
of
the
IDE.
You
have
a
openshift
Explorer
down
here
where
I'm
showing
you
here
is
my
project
on
container
application
platform.
You
can
see
everything
you
have
deployed.
Here's
the
grant,
PHP
app!
You
can
actually
do
port
forwarding.
You
can
look
at
the
pod
log.
You
gotta
set
your
OC
command
line
tools.
Let
me
do
that
real
quick
oops,
so
let
me
just
browse
for
it.
We're
actually
already
have
it.
A
So
Eclipse
needs
to
know
where
your
OC
command
line
tool
is
to
run
some
of
the
integration,
so
I'll
click
OK
and
then
apply.
And
now,
if
I
come
in
here
and
look
at
you
know
the
pod
log
it'll
pop
open
the
pod
log
inside
of
the
Eclipse
IDE.
So
you
can
do
cool
things
like
port
forwarding.
You
look
at
the
properties
and
do
all
kind
of
stuff
inside
of
the
integration.
A
A
Database
running
right,
so
if
we
look
at
this
Kuril
database-
and
we
look
at
this
pod,
we
can
see
that
my
environment,
here's
the
environment
variables
that
we
have
now
what
we
need
to
do:
Co
user
password
in
database
if
I
want
to
hook.
This
up
is
go
over
to
our
PHP
pod
and,
let's
just
you
know,
look
at
the
environment
here
and
grep
for
MySQL.
A
You
can
see
that
by
default,
when
I
added
the
MySQL
database
to
my
project,
it
added
some
environment
variables
to
my
running
deployment,
config,
okay
and
so
what's
left
for
me
to
do
as
a
user
is
to
just
come
on
to
the
command
line
tool
here
and
do
OC
get
DC
and
it's
called
grant
PHP.
This
is
my
deployment
config.
This
is
what
defines
the
truth
of
my
running
application
and
I
can
do
OC
e
and
V
and
set
an
environment
variable
on
my
feet.
A
A
If
we
go
back
to
the
overview
you'll
see,
it's
actually
deploying
a
new
version
of
my
application
out
and
that's
because
the
truth
of
that
application
changed
it
needed
that
environment
variable
in
order
for
it
to
be
in
a
good
state
and
because
it
wasn't
there,
it
went
ahead
and
redeployed
it
and
added
that
environment
variable
I
hope
that
makes
sense,
but
you
would
simply
just
add
those
environment
variables
to
your
application
and
then
you
would
connect
to
it
via
your
code.
Just
like
you
normally
would
all
right.
So
let's
go
back
to
our
project.