►
From YouTube: Magento Cloud Demo - Cloud Docker 1.0 with Michael Casey
Description
In this Cloud Demo, Michael Casey will discuss the new feature of Cloud Docker 1.0 release:
- New entry points
- New functionality
- Plans for the next releases
B
B
Just
a
quick
overview,
what
is
Magento
cloud
docker,
it's
a
doctor
composed
configuration
builder
and
also
has
lots
of
images
and
good
defaults
for
Magento,
as
pre-built
docker
containers
for
PHP
in
genetics,
varnish
right
at
elasticsearch,
etc.
So
all
the
same
services
that
you
would
have
on
the
cloud,
or
at
least
most
of
them
I,
don't
thing
to
note
is
that
varnish
is
not
on
the
cloud
we
have
fastly
instead,
which
is
a
little
bit
like
a
beefed-up
version
of
varnish.
So
varnish
is
not
the
exact
same
as
fastly.
B
There's
some
differences
there,
but
it
does
give
you
sort
of
that
same
idea
of
full
page
caching.
We
have
a
lot
of
good
default
configuration
settings
with
cloud
dogger
for
Magento,
so
you
have
a
good
out-of-the-box
experience.
You
have
to
change
too
much
and
it's
historically
similar
to
Magento
clouds.
So
you
really
get
to
have
a
good
testing
experience
before
you
push
the
cloud
you
can
make
sure
things
work
on
Cloud
docker,
and
that
gives
you
a
little
more
confidence
that
it'll
work
on
the
edge
of
the
cloud
as
well.
B
B
C
B
It
includes
all
the
services
you
need
to
run
Magento,
so
you
don't
have
to
install
a
bunch
of
services
on
your
host
machine
or
manually,
configure
them
or
cobble
together
a
bunch
of
different
docker
containers.
It
use
docker.
So
it
simplifies
the
development
setup.
You
can
have
different
projects
with
different
containers
and
so
on.
B
So
we
have
this
release
that
we
came
up
with
a
few
months
ago,
Magento
cloud
docker
1.0,
and
that
was
pretty
big
release.
We
released
a
whole
bunch
of
features
which
I'll
be
previewing
here
in
a
minute
previously,
we
had
all
of
the
cloud
doctor
functionality
bundled
with
ICI
tools,
2000
2.0,
but
as
of
easy
tools.
2002
8.1.
Now
we
have
been
diptych
Locker
code,
all
in
a
separate
package.
B
B
We
have
updated
many
or
all
the
containers,
images
that
we
have
so
PHP
in
genetics,
etc.
With
improvements,
we've
disabled,
cron
by
Deepak
Ron,
a
container
and
cron
automatic
Quran
running
by
default
course.
This
can
still
be
run
manually
and
we
have
added
a
separate
post
deploy
command
and,
of
course,
you
can
always
view
dev
Docs
to
see
the
full
change
list
and
at
the
end
of
the
slideshow
there'll
also
be
a
lot
more
links
to
dev
docks
with
backers
and
compatible
changes,
and
so
on.
B
B
It
has
a
separate
repository,
but
you
don't
have
to
do
anything
different
on
your
end
as
a
developer
or
if
you're,
you
know,
you
want
to
have
the
functionality
of
Magento
cloud
docker.
It
is
bundled
because
yeah
mr.
Crocker
is
a
dependency
of
EC
tools,
2000
3.1,
so
it's
really
just
a
total
reorganization.
As
far
as
being
convenient,
it's
still
convenient
it'll
still
be
an
out-of-the-box
experience
where
you
have
that
cooking
meet
automatically.
B
Here's
an
example
of
how
it
was
before
with
EC
tools:
2000
3.0.
You
can
see
that
the
dr.
folder
within
this
SRC
directory-
you
have
this
docker
folder.
As
we
moved
to
2000
2.1.
You
can
see
that
dr.
folder
is
no
longer
there
and
we
now
have
a
separate
directory,
a
separate
repository
for
digital
cloud
docker,
and
this
is
one
dot
o
with
its
own
code.
B
Changed
and
probably
the
command
that
you'll
run
the
most
is
the
docker
bill,
whether
the
build
compose
command,
and
this
is
what
actually
generates
the
docker
compose
ml
file.
With
all
the
configurations
we
need
to
run
docker
compose
up.
So
previously
it
was
vendor
been
easy
tools.
This
was
as
easy
tools:
2000
2.0
you
had
the
doctor
in
namespace
and
the
build
command
now.
Ec
docker
has
its
own
command.
That
still
vendor
been
this
time,
is
e
ste
docker
and
then
build
compose
many
of
the
command-line
options
that
you
would
specify
on.
B
Dr
build
also
work
for
both
compose,
but
there
are
some
changes,
so
it
can
be
good
to
check.
You
can
just
run
h
or
help
on
these
and
just
to
make
sure
if
you
do
have
any
shell
scripts
or
something
that
you
had
specific
options
with
it.
It's
just
good
to
check,
but
many
of
them
are
similar,
but
we
do
have
some
additions
is
a
lot
which
I'll
cover
here's
an
example
of
how
it
was
before
with
easy
tools
mm
mm.
We
have
two
vendor
bin
easy
tools.
B
Doctor
build
HP
here
in
this
example,
I'm
running
7.2
and
I
wanted
to
do
developer
mode,
and
then
you
can
see
the
configuration
was
built,
and
then
here
is
just
you
don't
have
to
read
everything
on
this
page,
but
this
is
just
the
first
two
lines
of
the
docker
compose
a
ml
file
generated
from
that
command
and
then
here's
doing
it
with
the
new
way
with
easy
tools.
Who
doesn't
do
that?
B
One
which
includes
the
Magento,
clad
docker,
one
dot
o
you
can
see
I'm
ready,
see
doctor,
we
have
build
composed
and
actually
these
commands
happen
to
be
the
same.
But
there
are
some
changes.
Some
additions
as
well,
but
you
page
be
so
much
developer.
Configuration
was
built
and
then
here's
the
doctor
composed
animal
from
the
new
way
with
mention
declared
docker
1.0.
B
So
we've
disabled,
a
cron
container
by
default
cron
processing,
can
be
pretty
intensive,
especially
if
you're
running
Modesto
cloud
doctor
in
a
VM.
For
example,
if
you're
like
on
a
Mac
and
you're
running
a
cloud
docker
on
your
Mac,
then
it'll
actually
go
through
a
VM
and
there's
some
other
scenarios.
And
basically
you
know
sometimes
you're
running,
multiple
machines
or-
or
you
know,
you're
running
you
know,
you're
not
on
a
super
fast
machine
or
whatever
it
may
be.
Cron
processing
can
be
pretty
intensive,
so
we
disabled
that
by
default
for
a
mention
of
cloud
docker.
B
Of
course
you
know
if
you're
running
cron
run
manually.
That's
that's
still
a
hundred
percent
functional
there's,
there's.
No
reason
why
that
won't
work,
but
if,
for
some
reason
you
do
want
to
test
Cron's
or
you
do
you
still
like
having
the
Cron's
run
automatically
just
like
they
would
on
magenta
cloud,
then
you
can
just
use
the
with
cron
command
I'm
sorry
option
on
the
build
compose
command.
So
that's
just
a
change
in
defaults.
You
still
have
that
functionality.
If
you
like
it,
here's
an
example
of
how
it
was
before.
B
Let's
easy
tools:
2000
2.0,
you
see,
the
cron
container
was
made
and
it's
configured
as
all
the
volumes,
etcetera
and
then
the
crontab
you
can
see
in
this
case
this
cron
that
I
had
set
up.
That
was
running
every
minute
that
could
be
I
could
add
quite
a
bit
of
load
to
my
development
environment
and
then
here's
the
default
with
the
magenta
cloud,
docker
1
dot.
Oh,
you
can
see
pattern,
I
searched
for
cron
and
it
says
pattern
not
found
crime.
B
B
You
know
dr.
PHP
said
about
you
CLI
without
any
more
version
information,
but
now
we
actually
have
major
minor
versions
on
many
of
these
images,
so
that
helps
preserve
backwards
compatibility.
If
we
want
to
make
improvements,
then
we
can
go
ahead
and
just
increment
the
version
number
and
any
existing
setups.
You
have
won't
be
broken
by
those
changes,
so
it
just
helps
make
the
experience
better.
B
Overall,
if
you
are
using
to
cloud
docker-
and
you
want
to
make
sure
you
get
the
latest
updates,
all
you
got
to
do
is
run
composer
update
and
the
next
time
you
build
your
config
with
the
config
build
command.
Then
it
will
include
whatever
versions
that
it
that
it
can
either
pads
as
latest
but
any
but
anything
configuration
you
already
have
will
stay
the
same
so
that
won't
be
broken
by
anything.
B
See
here
is
how
it
was
with
easy
tool:
2000
3.0.
You
can
see
here
that
there's
the
old
images
you
can
see
throughout
an
example,
for
example,
here's
fpm
that
handles
the
PHP
code
and
it
has
F
p.m.
it
doesn't
have
any
version
number
same
for
build,
CLI,
etc
and
then,
with
majestic
cloud
doctor
100
now
you
can
see
there's
one
dot,
oh
and
yeah,
throughout
build
fpm,
etc.
B
You
can
browse
the
all
the
different
versions
we
have
on
docker
hub
with
the
Magento
user
on
docker
hub,
but
there's
not
really
much
need
to
go
browse
manually.
They
are
there
if
you're
curious,
but
really
easy.
Dr
both
compose
will
take
care
of
all
that
for
you.
So
it's
not
super
important
that
you
don't
file
through
them
all,
but
they
are
there
if
you're
curious.
B
Here's
an
example
of
docker
hub
with
the
I
picked
the
PHP
container,
for
example.
Here
there's
the
magenta
user
admitted
to
a
clinic
or
PHP
that
image,
and
you
can
see.
We've
got
one
of
the
versions
down
there
and,
if
I
scroll
down,
then
you
can
see
here's
some
1.1
containers
that
we've
really
so.
Actually,
we've
already
been
utilizing
this
to
make
improvements
without
making
any
backwards,
incompatible
changes.
B
Some
of
the
improvements
we've
made
to
the
PHP
image
we
include
nodejs
now
by
default.
So
if
you
have
any,
is
especially
useful
during
the
build
process,
if
you
have
any
like
JavaScript
compilation
or
anything
like
that,
that
uses
no
NPM
regret
CLI,
then
that
won't
work
with
the
PHP
image.
So
you
won't
have
to
do
any
manual.
Changes
to
your
docker
configuration
anything
like
that
and
we
now
support
ion
cube,
which
is
a
if
you
don't
know,
it's
basically
a
encryption
for
PHP
code.
So
but
none
of
them,
like
official
Magento
code,
does
this.
E
B
E
B
Made
updates
to
our
web
container
as
well,
which
is
sometimes
called
the
nginx
container.
You
can
customize
the
image
next
configuration
now
without
having
to
do
any
crazy
image.
Name
stuff.
A
building.
You
can
add
a
you,
can
follow
this
documentation
here.
I'll
show
you
an
example
in
just
a
moment
where
you
can
add
custom
engine,
ex-cons
and
Vienna's
comp
directors
and
also
Auto
generates
an
SSL
TLS
certificate.
B
So
if
you're
doing
testing-
and
you
want
to
test
SSL-
which
is
often
enabled
you
know-
we
much
always
enabled
on
on
Magento
sites,
then
that
all
that
will
be
supported
out
of
the
box
as
well,
and
here's
an
example
of
a
custom,
nginx
comp
or
actually
the
way
you
would
include
it.
You
would
just
have
a
docker
compose
override
and
then
you
would
say
volumes
you
would
mount
the
nginx
conf.
B
Because
that's
what
Magento
functional
testing
framework
uses
it
allows
you
to
use
em
FTF
on
Magento,
glad
darker.
It's
just
a
command-line
switch.
It's
not
enabled
without
this,
but
you
can
just
do
with
selenium
and
that
will
build
they
can
configure
with
the
selenium
Tanner.
You
can
see
Deb
docks,
pull
need
full
details
on
that.
B
One
thing
we've
done
as
made
the
database
container
persistent,
so
sometimes
people
like
to
do
docker
compose
down
and
they're
kind
of
shocked
when
their
database
is
gone.
So
we
made
it
a
persistent
volume
volume.
Actually.
So
here's
an
example
I'll
give
you
some
context
here:
I
did
docker
compose
up
D
and
then
I
did
dr.
Gillespie
s
just
to
show
that
my
containers
were
indeed
running.
B
B
So
if
I
do
docker
compose
down
it
scrolled
up
here,
but
I
did
down
without
the
V
I
didn't
it
removed
all
those
containers,
but
then
the
volumes
are
still
remaining,
so
that's
with
regular
down
and
then,
if
you
run
down
V,
which
I
did
here
now,
I
can
put
it
down
V,
but
you
can
see
it
removed.
The
volumes
also
remove
the
networks,
but
then,
when
I
do
dr.
volume
LS,
you
can
see
that
those
volumes
are
removed.
B
So
so
really,
if
you're
wanting
to
destroy
the
database,
then
you
can
just
do
down
P,
but
yeah.
Keep
in
mind
that
down
in
general
does
destroy
the
containers
and
everything
in
them.
So
we
just
made
the
database
container
base
volume,
persistent
and
then
down.
V
will
actually
destroy
the
volume
as
well.
B
B
B
B
B
I'll
just
show
you
an
example
of
the
code
here,
so
this
is
the
middle
declared
our
repository
with
the
commit
before
we
made
the
change
you
can
see
here.
Here's
the
cloud
build
in
cloud
deploy,
commands,
there's
no
separate
post
applied
command
and
if
we
look
at
this
cloud,
deploy
command
here,
look
at
the
color
real,
quick
at
least.
Actually
this
is
all
of
it.
You
can
see
it
runs
the
win
hooks
deploy
and
run
expose
to
place.
This
is
the
old
version
before
and
that
we
made
the
change.
B
So
it
was
really
just
doing
two
things
in
one
and
now,
with
the
new
version
you
can
see.
This
is
branch
1.0
here
on
the
top
left.
We
do
run
hooks,
deploy
and
that's
it,
and
then
we
have
a
separate
command.
You
can
see.
This
is
the
directory
for
one
dot.
Oh,
we
have
a
separate
command
proposed
to
play
now,
so
you
won't
have
to
in
most
cases
look
at
this
manually.
B
So
we
increased
the
TLS
timeout,
so
we
use
pound
as
a
TLS,
proxy
or
magenta
cloud.
Docker
and
pound
has
a
while
to
configure
those
subversion.
We
were
using.
The
default
configuration
had
a
like
a
connection
timeout
or
time
between
bites
timeout
of
15
seconds
and
if
you
were
running
a
particularly
complicated
site
or
if
your
system
was
kind
of
slow
or
whatever
the
case
may
be,
you
know,
development
environments
can
be
varied,
I
could
timeout
on
solar
systems.
B
So
if
you
were
trying
to
access
the
admin
panel
or
something
like
that,
not
everyone
had
this
problem
that
some
people
did
so
now.
It
has
a
default
for
300
seconds.
So
that
should
be
enough
to
really
make
sure
that
the
site
was
fine,
which
is
really
nice,
because
I've
actually
experienced
that
myself
and
this
was
submitted
by
Matthew
Tina's
alert
technology.
So
we
appreciate
all
the
contributions
in
the
community
and
that's
really
great
to
see
that
kind
of
stuff.
So.
B
Here's
an
example
of
the
TLS
container,
the
image
image
source
code
and,
of
course
this
is
all
built
into
the
image,
so
you
won't
have
to
mess
with
this
most
the
time.
It's
just
an
example.
We
have
the
pound
dot
CFG
now
so
that
we
can.
Actually,
you
know,
speed
that
into
the
into
the
container
and
have
it
use
that
config
as
opposed
to
the
default.
B
Here's
the
pound,
dot
CFG
file,
use
to
snip
it
from
it.
You
can
see.
Has
you
know
most
of
the
default
stuff,
but
then
it
also
has
this
variable
here
for
timeout.
So
previously
this
was
just
set
to
15
seconds,
and
now
we
have
it
as
a
variable,
and
if
we
look
at
the
docker
file,
then
you
can
see
in
V
timeout
300.
That's
our
that's!
Our
default
timeout!
No.
B
So
we
and
other
things
after
one
dot.
Oh
and
I-
have
some
changes
to
preview
here.
You're,
pretty
exciting
one
of
the
bigger
ones
is
the
universal
configuration
file
and
that'll?
Let
you
run
magenta
cloud
docker.
Ultimately,
our
goal
is
to
make
it
so
you
can
run
image
in
the
client
docker
without
needing
any
of
the
magenta
clouds
specific
configuration
files
we
want
to
support.
You
know
more
use
cases
for
magenta
cloud
docker
and
make
it
more
of
a
generic
solution
across
the
Michener
community.
B
B
We're
gonna
have
X
dot,
X
debug
pre-configured
on
developer
mode
by
default.
So
that's
great.
A
lot
of
people
use
XD
bug,
especially
when
they're
developing
code
I
know
I,
do
so
being
able
to
use
that
with
magenta
client
docker
in
a
seamless
way
is
a
priority,
so
that'll
be
really
nice
for
the
development
experience
overall.
Of
course,
the
production
mode
will
still
be
the
way
it
is
now
where
it's
not
enabled
automatically.
This
was
submitted
by
Matthew
bean
as
well.
So
thanks
for
that.
B
Witch
so
you
don't
actually
need
PHP
installed
on
the
host
in
order
to
initialize
magenta
Claire
docker.
Currently
you
have
to
use
PHP
to
run
the
built
compose
the
build
command
because
it
actually
is
a
PHP
script
itself,
so
we're
gonna
leverage
docker
to
containerize
that
build
process
as
well,
so
we're
coming
up
I
believe
we
have
some
shell
scripts
for
working
on
where
it'll
pull
the
image.
B
And
we're
going
to
make
it
so
automatic
varnish
caching
is
enabled
currently,
when
you're
going
to
the
procedure
on
dev
docks
for
either
the
developer
mode
or
production
mode,
there's
some
manual
command.
You
have
to
run.
Of
course
you
can
just
copy
and
paste
these
from
Deb
docks,
but
there's
still
many
new
commands
where
you
have
to
go
and
run
I
can
fix
that
caching,
application
etc
and.
B
Going
to
make
this
just
a
built-in
part
of
the
build
process,
that's
something
we're
working
on!
It's
interesting!
You
know
we
want
to
make
sure
that
if
you,
if
the
container
is
not
present,
that
we
don't
select
it
so
there's
some
interesting
ways
we're
looking
at
solving
that
problem,
but
that
is
something
we're
working
on.
B
Alright,
so
takeaways
with
our
changes
and
updates,
we
want
to
have
better
platform
support
from
Ajinca
cloud
docker
window
across
Mac,
Linux
and
windows,
supporting
more
developer
environments
so
like
whether
you
are
cloning
it
within
the
cloud
repo
or
whether
you're
running
Magento,
and
you
don't
have
clone
magenta
cloud
repo.
We
want
to
have
we're
trying
to
have
more
support
for
that
when
I
have
a
simpler
setup
process
so
that
you
don't
need
to
have
so
many
prerequisites
installed
or
manual
commands
being
run,
then
just
a
smoother
overall
experience.
B
Deb
Docs
has
lots
of
details.
It
covers
everything
I
mentioned
and
more
so
you
can
look
here
at
the
release:
notes
a
full
list
of
backwards,
incompatible
changes,
just
here's
the
guide
for
doctor
development
and,
of
course,
here's
the
demo
Docs
link
overall,
which
you
can
just
use
the
search
box
and
find
lots
of
good
stuff.
And,
as
always,
you
can
go
to
the
cloud
docker
sock,
Channel
and
get
help
there
from
the
community
and
also
we
like
to
help
out
there
and
when
we
can
as
well.
B
D
B
C
B
We've
had
that
there
and
we
intend
to
keep
it
there,
so
I
mean
I
would
say
yes,
I'll
need
to
check
with
the
documentation
team
and
see
if
we
need
to
add
more
on
that
I
think
it
was
originally
just
a
pretty
simple
command.
So
with
you
know,
you
could
just
check
the
source
code
pretty
quickly
and
I
think
it
might
still
be
so
I'm
not
sure
exactly
how
much
Doc's
work
we're
doing
on
that.
But
I'll
check
on
that
for
you
for
sure.
E
Have
a
question:
is
there
then?
Obviously,
it's
already
reading
some
configuration
based
on
cloud,
so
the
doc
digital
touch
in
the
diagram
file
for
some
things,
but
not
others.
So,
for
example,
the
default
database
password
is
just
dumped
into
the
docker
compose
file.
But
if
someone
had
a
cloud
configuration
where
it
was
already
in
tomatotopia,
it's
not
this
isn't
at
all.
B
I
know
that
the
OPN
is
used
by
EC
tools
during
the
build
process
and
so
on
the
deploy
process.
So
we
might
not
have
picked
up
everything
and
put
it
into
mid
to
cloud
docker
as
well.
But
I
know
that
going
forward.
Our
goal
is
to
have
a
hierarchy
of
configuration
where
like,
for
example,
the
universal
configuration
I
was
talking
about.