►
Description
In this demo, Russell Albin will demonstrate how to set-up xDebug configuration on Magento Cloud.
A
Once
again
welcome
to
our
bi-weekly
demo
sessions
today
we
have
russell
albin
from
blue
acorn,
talking
about
debugging
process
on
magento
cloud
so
fulfill.
This
is
a
very
valuable
skill
to
have
just
in
case
when
you
have
issues
so
russell
thanks
for
for
coming
today
and
taking
your
time
to
prepare
the
presentation
and
giving
work
to
you.
B
B
It
presented
itself
on
the
production
environment
for
a
pro
a
pro
production
environment,
and
it
was
enough
of
a
bug
that
it
was
going
to
have
us
delay
the
launch
and
up
until
this
point
I
I'd
use
remote
debugging
for
like
integration
environments,
but
I'd
never
done
it
on
a
pro
production
environment,
and
so
I
went
through
the
dev
docs
and
they
were
very
helpful.
But
I
got
to
a
point
where
I
was
blocked
because
it
wasn't
clear
what
the
process
was
to
actually
make
this
work.
B
B
B
B
B
B
B
C
B
B
C
B
That's
a
lot
more
lots:
better:
okay,
okay,
so
I'm
gonna
have
to
toggle
between
my
different
windows
that
way
it's
nice
and
big
for
everybody,
okay.
So
as
far
as
creating
your
server
once
again,
just
use
the
url
of
your
project
for
the
name
that
that
should
help
you
differentiate
it
for
the
host,
it's
going
to
be
the
url
minus
the
https,
or
anything
like
that,
it's
literally
just
the
just
the
url
and
in
my
case
I'm
using
a
cloud
project.
B
B
B
B
B
So
it's
just
the
word
phpstorm
and
once
again
make
sure
you
pick
your
server
from
the
servers
that
you
just
created
and
once
you've
done,
that
all
you
have
to
do
is
click
ok
and
you've,
basically
gotten
about
as
far
as
you
need
to
go
as
far
as
php
storms
configured.
So
we
have
the
clouds
ready
because
we
added
the
flag
to
xdebug
and
we
deployed
it.
B
B
B
So
that's
the
easy
one
so,
although
it
seems
a
little
daunting,
it's
really
not,
but
that's
the
easy
one
to
do,
because
there's
one
app
server
that
you
have
to
connect
to
the
reason
why
the
pro
environments
for
staging
and
production
are
a
little
more
tricky
is
that
there
are
three
or
more
app
servers
and
that
and
then
they'll
also
have
to
remember
that
there
are
the
the
ide
key
for
x.
Debug
is
not
php
storm.
B
You
have
to
create
a
support
ticket
with
magento
and
the
infrastructure
team
has
to
go
and
fetch
the
keys
and
what
they'll
do
is
they
will
put
that
key
on
the
production
environment
or
staging
wherever
you
asked
to
have
it
enabled
at
without
that
step,
you're
unable
to
debug
production
and
staging,
which
was
one
of
my
blockers.
When
I
did
this,
I
thought
you
could
just
use
phpstorm,
but
I
searched
up
and
down
the
server.
I
couldn't
find
the
key
anywhere
and
then
it
just
turns
out
that
magento
support
had
to
provide
that.
B
So
if
you
do
have
to
do
this,
make
sure
that
you
create
a
ticket
as
soon
as
possible
and
let
them
know
that
you
know
what
your
intentions
are
in
which
environment
and
then
they
will
put
the
key
specific
for
that
environment
on
the
server.
They
won't
give
it
to
you
in
the
ticket.
They'll
they'll
make
you
go,
get
it
from
the
server.
B
So
for
pro
environments,
there's
just
a
little
bit
of
a
nuance
that
you
have
to
be
aware
of.
Once
again,
you
have
to
know
that
there
are
three
or
more
app
servers.
You
can
have
upwards
if
I
think
nine
is
the
biggest
one.
I've
ever
worked
on
the
other
thing
when
you
ssh
into
a
production
environment,
and
you
try
to
look
for
xdebug-
it's
not
going
to
exist,
I'm
sorry
yeah
for
xdebug
and
php.
It's
not
going
to
exist,
and
it's
because
that
service
runs
on
another
container.
B
D
B
D
B
B
B
And
with
this
ps,
fau
wx,
and
then
you
pipe
grab
x,
debug
and
then
you
pipe
grec
v
grep
with
that
you'll
notice
that
there
are
x,
debug
configs
here.
So
if
you
run
this
command-
and
you
see
these
two
or
similar
lines,
you
know
that
you're
on
the
right
path.
That
means
the
the
environment
is
ready
for
you
to
test.
B
B
B
B
B
So,
if
you're
unclear
for
pro
environments,
it's
app
slash
and
then
the
project
id,
but
once
again
you
can
verify
that
by
once
you've
logged
in
you
can
just
do
pwd
and
wherever
you
log
in
for
magento
cloud.
That's
your
route
and
that's
where
you
want
the
where
you
want
this
configuration
to
be
so
you
want
it
to
be
app
slash
and
then
the
project
id
once
you've
all
done
that
and
you're
happy.
B
The
next
step,
we're
going
to
do
is
we're
going
to
add
a
configuration
for
the
php
remote
debug
and
by
doing
that,
you're
going
to
use
a
little
plus
arrow
you're,
going
to
go
down
to
php
remote
debug,
and
because
I
set
this
up
ahead
of
time,
the
name
can
be
once
again
whatever
you
want.
This
is
just
a
some,
a
cue
for
you
to
find
it
in
the
future.
B
B
So
this
is
the
the
ide
keys
that
you're
gonna
need
so
that
you
put
here
and
then
when
you're
all
happy,
you
click,
ok
and
then
the
next
step
is
to
prepare
your
urls
for
how
you're
going
gonna
connect.
So
you
have
to
do
the
port
forwarding
again,
but
you
have
to
do
it
for
all
three
application
servers
and
then
also
be
wary
that
you
can
only
have
one
person
debugging
at
a
time
and
magento
provide-
and
this
is
another
thing
that
blocked
me.
B
I
was
unclear
on
the
syntax
on
how
to
kick
someone
off
who
might
be,
who
might
have
left
their
debugger
connection
running,
and
so
there
are
a
total
of
six
commands,
but
there
are
two
for
each
application
server.
The
first
one
basically
gets
rid
of
any
other
x,
debug
connection
that
was
made
and
then
the
second
one
does
the
port
forwarding
to
connect
you
to
the
environment.
So
that
way
you
can
you
could
do
your
your
task.
B
So
here's
my
little
text
file,
which
I
created
to
help
expedite
the
process,
so
this
first
one
is
going
to
be
kicking
off
any
existing
ssh
connections
that
have
been
made
for
debugging
and
if
you
get
nothing
back
or
you
happen
to
get
some
response
back
either
way,
it's
fine
there's
really!
No
failure
on
that
one,
the
second
one
actually
does
the
port
forwarding
connection
for
you.
B
Three
okay,
so
now
I've
got
a
solid
response.
2021
looks
good
at
this
point.
The
other
variance
is
that
you
need
to
add
a
get
parameter
x,
debug
session
start
with
the
the
x
debug
key.
That
magento
provides
you,
so
this
is
different
than
a
slightly
different
than
what
we
did
for
the
integration
environment.
The
syntax
here
has
to
be
exactly
this,
and
so
we'll
just
copy
this,
maybe.
B
And
before
we
do
that,
just
make
sure
that
your
telephone
is
listening
for
connections
and
your
service
is
ready
and
that's
listening,
and
if
everything
is
hooked
up
properly
boom.
There's
our
debugger
picks
it
up.
Just
like
it's
supposed
to
and
command
line
is
the
exact
same
the
exact
same
pattern
so
as
we
did
on
integration.
B
B
Restarting
your
browser
and
then
on
pro
environments,
if
you
have
full
page
cache,
which
most
of
us
do,
the
other
trick
that
I
learned
is
sometimes
you
can't
just
hit
the
home
page,
it's
better
to
hit
like
customer
account,
login
or
check
out
some
non-cash
page
to
help.
You
make
sure
that
the
break
point
is
actually
hit,
and
I
think
yep
and
just
double
check
your
id
key.