►
Description
Deploy your First Application to Cloud Foundry - Dr Nic Williams, Stark & Wayne
You’ve heard the buzz about Cloud Foundry, but is it truly as easy for me to deploy my first application? Is it possible to run CF on my laptop? If I’m a student can I use Cloud Foundry? If I’m only new to software development can I use Cloud Foundry? If I’m shy and don’t like to ask questions can I use Cloud Foundry? You are asking good questions. Let’s do this together, right now. Dr. Nic of Stark & Wayne walks you through the process of deploying your first app to Cloud Foundry.
For more info: https://www.cloudfoundry.org/
A
Well,
excellent
thanks.
Everyone
for
coming
I,
firstly,
want
to
acknowledge
that
you've
all
relatively
sat
in
the
middle
of
the
room,
I,
don't
exactly
know
how
it
works.
Sometimes
you
can
have
a
group
and
if
there's
far
more
seats
than
necessary,
there's
just
a
different
vibe
you'll
get
a
person
over
there.
You'll
get
a
person
that
corner
and
then
I
feel
like
I
have
to
go
and
heard
that
Mike
Katz
come
on.
A
You
can
move
in
you're
awesome,
so
I
really
appreciate
that
we're
in
the
middle
and
I
want
to
share
something
that
I
have
benefited
from
since
I
started,
using
Cloud
Foundry,
2012
I
started
stuck
away
in
2012-2013,
but
really
I
before
Cloud
Foundry
I
was
using
Heroku
and
so
I've
benefited
from
things
like
build
packs
for
over
a
decade
and
I.
Think
it's
because
Heroku
and
Cloud
Foundry
have
always
made
sense
to
me.
I've
never
been
very
good
or
enthusiastic
about
evangelizing
it.
A
What
we're
gonna
talk
about
now,
because
what
to
talk
about
it
obviously
makes
sense.
You
know,
let's
talk
about
the
hard
stuff,
sorry
I'm
actually
doing
something.
I
did
a
YouTube
video
earlier
in
the
year,
which
I
think
was
still
one
of
the
first
times.
They've
ever
really
said
all
right,
let's
play
with
Cloud
Foundry,
because
yeah
I
always
just
assumed
someone
else
would
do
it,
but
you
know
you're
gonna
have
your
turn.
So
I'm
used
Cloud,
Foundry
I'm
a
I,
see
if
push
all
the
time
and
happy
to
share
it.
A
So
if
this
is
your
first
time
and
then
you're
gonna
need
the
CLI
and
I'm
gonna
do
these
commands
for
you.
This
is
not
a
hands-on
lab,
but
then
you
know
there
is
the
the
CLI
you're
gonna
need
to
install
it.
There
is
a
new
one
coming
out
and
for
anyone
watching
the
video
at
some
point,
the
time
see
if
seven
might
be,
that
that's
the
one
you
get,
but
the
instructions
and
the
commands
I
believe
will
keep
working
through
CF
v
seven.
A
Now
we
are
going
to
talk
to
a
cloud
foundry,
so
cloud
foundry
is
fundamentally
a
running
system
running
somewhere
else,
whilst
our
inner,
you
know
we
look
at
it
through
the
patch
the
eyes
of
our
command-line
tool.
It
is
actually
talking
to
a
hosted
service
running
somewhere
and
we're
going
to
log
into
that
now.
I
will
come
back
to
this
slide
if
you're
looking
for
a
Cloud
Foundry
here
are
six
of
these
sort
of
certified
cloud
boundaries.
I
guess
clad.
A
Also
it
builds
it
and
runs
it
the
same
way
that
many
people
run
it
in
production,
which
is
using
a
tool
called
Bosh
so
later
on.
If
you
become
interested
in
how
it
works,
you
can
start
playing
with
it
all
on
your
laptop,
which
could
be
quite
kind
of
interesting,
none
of
which
we're
going
to
do
today.
Today
we
are
CF
pushing
like
champions.
A
So
there
is
different
ways
so
now
I've
just
copied
the
output
from
from
a
few
runs
cf
help,
but
there
are
a
bunch
of
flags,
and
so,
if
we
I'm
going
to
for
today,
I'm
going
to
use
pivotal
z'
in
part
because
it's
been
out
the
longest
I've
just
used
it
the
longest
I,
you
know
I
always
sometimes
I,
don't
think
enough.
People
give
enough
respect
to
pivotal
for
all
they're
there.
A
The
money
they've
spent
on
Cloud
Foundry,
so
today
I'm
going
to
use
pivotal
z',
but
everything
we
do
should
work
very
similarly
and
all
the
others
all
right,
so
I'm
going
to
have
login
know
typically
I
have
in
my
history
this
command
or
a
version
of
it.
So
it's
got
the
a
flag
which
is
going
to
point
to
which
cloud
foundry
I'm
going
to
talk
to
maybe
I'll
specify
an
organization
there,
oh
flag.
A
My
account
happens
to
have
a
couple
of
different
organizations,
so
I'm,
just
sort
of
short-circuiting
and
I
already
know
what
space
I'm
going
to
go
into
because
I've
done
this
and
our
before
it
turned
up,
but
the
most
interesting
one
here
is
the
SSO
flag.
Many
people
might
never
have
even
tried
this
flag
and
what
this
means
is
I'm
not
going
to
put
my
username
password
into
my
terminal.
A
So
when
I
run
this
I
get
given
this
URL
they'll
just
pop
that
up,
I've,
already
logged
in
so
I
feel
like
I
might
have
short-circuited
something
cheated
you
out
of
so
normally
you
would
need
to
login
and
pivitol
'he's
got
there.
You
AAA
configured
this
this
way,
so
I
need
to
first
just
confirm
that
to
the
account
and
then
and
the
reason
I
like
that
SSO
flag
is
I,
could
use
one
password
in
my
browser
and
I
just
feel
a
lot
more
secure
about
this
process.
A
Then,
having
my
password,
you
know
in
my
history,
I
get
this
copy
and
paste
that
into
there
and
now
I'm
logged
in
your
two-factor
authentication.
That's
my
process
I,
like
that.
It
means
I'm
not
sort
of
lured
into
putting
my
password
in
my
terminal,
because
it's
fast
and
and
we're
logged
in
so
the
next
thing
we're
gonna
do
is
deploy
an
app
which
is
the
literal
title
of
the
talk,
so
leave
that
till
the
end.
Like
it's
a
big
surprise
in
order
to
deploy
an
app,
we
need
one
now.
A
A
I'm
gonna
pick
Ruby,
oh
I,
like
Ruby,
and
it's
small
and
it's
easy
to
look
at,
and
you
know,
there's
not
a
lot
of
things
and
you'll
go
a
different
language,
just
how
cool,
because
if
you
can
deploy
with
if
you're
a
Java
person-
and
you
can
push
a
Java
app
now
that
the
deploying
part
is
taken
care
of,
you
can
now
start
to
dabble
in
other
languages.
Just
because
it's
you
know
the
deployment
parts
easy.
The
only
part
you've
got
to
figure
out.
What
does
a
ruby
app
look
like?
A
A
It
is
literally
tiniest
little
app.
You
could
imagine.
I
have
a
dependency.
Gemfile
is
the
Ruby
equivalent
of
like
package
Jason
for
jar
for
JavaScript
or
nodejs
palm
or
there's
a
list
of
dependencies,
and
my
app
is
in
this
config
dot.
Are
you
I'm
super
tiny
little
app
I
mean
even
if
you
don't
know
Ruby,
you
can
figure
what
this
does
and
right
here,
it's
gonna
say
hello,
world.
That's
what
we're
looking
forward!
A
There
was
a
very
funny
Twitter
message
once
that
was
a
joke
where
the
sysadmin
has
come
to
that
to
the
developer
and
said:
doesn't
work
and
the
developer
said
works
on
my
laptop
and
the
sister
had
been
said:
will
they're
back
up
your
email
because
that's
gone
into
production,
so
we
want
to
get
off
your
laptop
and
want
you
just
to
live
in
in
production,
but
first
and
foremost,
you
probably
want
to
run
on
your
laptop.
So
let's
show
you
some
Ruby
things
that
you'll
never
type
again.
A
So
let's
run
my
little
local
app,
what
don't
we're,
not
99
donno?
Why
did
1990
Fedders
not
useful,
but
they're
they're
app
working
like
a
jiffy,
all
right,
so
I
needed
to
know
all
that
stuff
I
needed
to
know
the
Ruby
way
of
running
apps
I
needed
to
type
it,
but
as
we
move
on
to
pushing
an
app
we'll
discover
there's,
so
we
don't
need
to
know
this
stuff.
Cloud,
Foundry
and
bill
packs
know
this
stuff
for
us.
A
Let's
just
make
this
look
clean,
see
if
push
tiny
Ruby
doesn't
need
to
give
it
a
name-
and
this
is
a
name-
that's
specific-
to
the
space
that
we're
in
Cloud
Foundry
I'm
not
going
to
cover
all
the
spaces,
but
I
do
need
just
to
give
it
a
name
and
that
will
attempt
to
give
it
a
route.
But
you
know,
let's
just
go
with
a
random
route.
A
So
the
first
thing
it's
attempts
to
the
first
thing
it
does
is
serve-
generates
a
random
route
that
is
available.
It
uploads
my
the
code
in
this
folder.
There
are
ways
to
ignore
files.
So
if
you've
got
like
a
big
logs,
folder
or
a
node,
NPM,
no
node
modules-
and
you
don't
want
to
upload
those-
there
is
a
dot
C
F
in
ignore
file
that
you
can
use.
So
you
really
don't
want
that
to
be
a
big
thing,
one
of
the
smallest
possible
things.
That's
faster
now.
Look
at
this!
This
is
super
interesting.
A
This
is
this,
is
you
know?
Well,
Cloud
Foundry
does
a
lot
of
great
stuff
we're
in
day
2
onwards.
This
is
fantastic.
This
business
of
you
just
give
it
some
files,
and
it
goes
to
all
these
things
called
build,
packs
and
says:
hey
which
of
you
know
what
this
is,
and
so
it
asked
the
Ruby
bill
package
net,
go
PHP
static
file,
Java,
it
asked
all
of
them,
and
the
Ruby
bill
pack
is
the
one
that
says.
A
I
know
what
that
is
now
specifically,
the
Ruby
build
pack
looks
for
a
file
called
gem
file
and
gem
file
dot
lock,
and
it
says
well,
if
you've
got
those
files,
I
assume
the
rest
of
it
is
a
ruby
file,
a
ruby,
app.
I've
got
that
if
it
found
a
package
dot
jason,
it
would
say,
then
the
ruby
app
would
probably
ignore
it.
A
A
ruby
build
pack
would
ignore
it,
and
the
node
build
pack
would
pick
it
up
and
so
bill
packs
in
this
way
of
plug-and-play
way
of
making
Cloud
Foundry
is
flexible
as
we
need
it.
So,
if
your
organization
wants
to
start
playing
with
rust
and
there's
no
rust
build
pack,
okay,
you
can
make
a
rust
build
pack,
there's
probably
three
of
them
on
the
Internet.
A
This
is
in
this
cloud
fairy.
The
list
of
ordered
so
they're
actually
done
in
that
order.
But
if
that
order
doesn't
suit
you,
you
can
actually
be
specific,
and
you
say
this
is
the
Bill
pack
and
I
will
do
that
soon.
For
you
first
one
wins
yep
all
right
did
we
deploy
her.
We
did
look
at
that.
Go
us.
So
there
is
the
URL.
A
And
there's
our
holo
world:
that's
our
holo
world
running
on
the
internet,
somewhere,
don't
care
where
you
know
the
last
thing.
I
care
right
now
is
where
it's
running
it
works
and
there's
this
pretty
fantastic.
You
can
see
that
it's
there
is
the
start
command
that
it
decided
for
us
is
going
to
work
for
us
and
interesting
that
it's
allocated
as
one
gig
of
ram,
and
yet
it
says
I
only
need
25
mega
the
stuff.
So
perhaps
we
can.
We
can
look
at
optimizing
that
in
a
moment.
A
So
when
we
push
we
can
be,
we
can
give
more
suggestions,
as
I
said
it
by
default.
It
allocated
a
one
gig
container
of
ram
and
the
reason
that
over
allocates
is
because
bad
things
happen.
When
you
run
out
of
RAM
it
just
things
just
die
when
you
run
out
of
RAM,
so
Clara
found
you
by
default,
allocates
a
lot
of
RAM
much
more
than
nearly
every
app
will
ever
need,
and
it's
left
you
to
scale
that
back
down
to
the
size
that
your
app
will
be
happy
with
the
ax.
A
Minus
B
flag
allows
us
to
be
specific
about
what
Bill
pack
or
Bill
packs
we
want
to
use
and-
and
it's
probably
a
good
idea
to
start
with
with
two
instances
now.
Obviously,
that
means
you've
got
twice
as
much.
You've
got
cost
something
in
some
in
some
way
you're
paying
for
this.
But
if
you
don't
start
with
the
idea
that
you've
got
two
containers
running
and
they
don't
share
memory,
they
don't
share
dis
space.
If
that
way,
you'll
be
forced
into
that
that
realization
that
this
is
how
things
scale
in
in
the
cloud.
A
A
A
A
And
it
would
push
that
up
again,
it'll
give
a
visualization
that
we've
changed
something
and
we'll
go
through
that
process.
Now,
when
it
does
this
a
second
time,
even
though
it's
a
tiny
app
and
it
did
very
little-
it
doesn't
even
faster
the
second
time
because
it
starts
to
cache
some
of
the
decisions
that
made
along
the
way
because
we
did
not
change
the
dependencies.
You
know
a
ruby
person,
but
we
have
a
library
called
Sinatra.
I
did
not
change
what
version
of
Sinatra
I
did
not
add
any
other
versions.
A
A
It
is
on
that
idea
of
multiple
instances.
If
you've
got
more
than
one
instance,
the
traffic
is
randomly
allocated,
so
should
they
each
the
containers
behave
differently
in
some
way,
different
traffic
will
go
to
each
one,
and-
and
sometimes
people
like
to
do
little
demos
well
they'll
print
in
a
number
and
approve
something,
but
just
to
be
clear.
We've
now
got
two:
they
don't
share
memory,
they
don't
share
disk.
Please
don't
write
to
those
things
all
right
now,
even
though
the
CF
push
command
did
all
that
magical
stuff.
A
It
gave
us
a
large
amount
of
RAM
that
we,
we
then
explicitly
came
down
and
said
we
want
it
less
ram.
It
only
did
one
instance
by
default,
even
though
two
or
more
is
better
and
it
didn't
decide
on
any
build
packs
up
front.
It
figured
that
out
during
staging.
There
were
flags
for
all
of
those
things,
but
I
would
ask
you
to
then
move
on
from
flags
and
to
create
a
gamble.
Father
describes
these
things.
A
It
gives
you
some
benefits
later
on
that
we're
not
going
to
get
to,
but
it
is
more
explicit
of
what
it
is
you
want
and
it
allows
you
to
document.
Perhaps
what
staging
app
looks
like
with
it's
URLs
and
perhaps
what
production
app
looks
like
when
it's
URLs
and
and
and
different
environment
variables.
So
there
is
a
command.
A
We
could
write
the
you
know
it's
a
Yambol
file
and
since
none
of
us
know
what
the
schemer
that
yellow
file
is,
they
very
helpfully
made
a
little
helpful,
app
a
little
command,
so
the
create
app
manifest
command
takes
the
app
that's
already
running
and
spits
out
the
ml
file
and
the
we
contribute
that
never
happened
so
now.
Everyone
knows
how
we
deployed
this
app.
A
So
that's
an
example
of
a
manifest
and
in
there
we
can
put
environment
variables,
so
we
could
add,
build
packs
and
we
can
make
make
changes.
So
let's
do
that.
That's
now
also
before
I
do
that.
So
now
we
don't
need
to.
If
we
look
at
CF
health,
we'll
see
that,
whereas,
if
f
path
to
manifest-
and
it
doesn't
say
the
default-
but
the
default
is
what
we
have
so
now-
I
don't
need
to
do
anything.
A
A
All
right,
a
really
nice
thing
about,
given
that
it's
a
big
multi-tenancy
thing
and
and
like
this
Cloud
Foundry,
is
not
run
by
me.
It's
run
by
someone
else.
I
can't
just
jump
onto
one
of
the
servers
rummage
around
looking
for
my
container
and
start
looking.
This
locks,
Cloud
Foundry,
is
fundamentally
a
multi-tenant
experience,
and
so
all
the
things
you
as
a
developer
or
an
operator
need
to
do
it
brings
those
to
you
it's
in
a
safe
and
secure
way,
logs
being
one
of
them.
A
A
If
you
want
like
big
history
of
logs,
that's
where
you
would
plug
in
third-party
logging
systems
Splunk
or
some
of
the
hosted
ones,
and
so
you
can
sort
of
see
that
it's
a
we've
got
here.
Container
number
for
container
number
one
can
enter
number
two.
You
know
mat
zero.
All
starting
up,
so
they
all
look
like
this,
it's
in
red,
but
there's
no
error
but
they're
all
just
starting
up.
The
other
way
we
can
do
logs
is
we
can
tale
the
logs
which,
but
is
the
default
command.
A
So
all
from
now
on
any
new
request
coming
in
any
new
logs
that
gets
spat
out
from
the
application
containers
will
show
up
there.
So
you
guys,
so
we
get
to
see
the
sort
of
a
request
metadata
for
that
Rick
for
the
request
and
any
of
the
application
logs
noteworthy
one
of
these
is
white.
One
of
these
is
red.
That
is
helpful
unless
you
are
a
red
white
colorblind,
but
it
is
the
standard
out
and
standard
error.
A
A
A
I've
written
one
or
two
of
these
myself
over
time,
lots
of
different
plugins,
sometimes
they're
for
a
point
in
time,
but
we
have
some
interesting
ones
around.
You
know
if
you
all
the
different
bill,
packs
being
used
helpful
to
figure
out
if
anyone's
using
older
plugins
but
bill
packs.
We
need
to
help
them
update
doctor,
just
look
at
the
apps
and
see
if
there's
any
errors,
but
the
one
I
want
to
show
you
that
might
be
one
of
the
first
ones
you
might
want
to
load
is
called
open.
A
The
CF
CLI
does
not
have
a
nice
way
just
to
open
an
app
into
a
browser.
Plugins
are
a
really
simple
way,
and
you
know
we
wrote
a
really
service.
One
of
the
first
plugins
ever
written
was
like
well,
we
just
want
to
open
something,
but
I
thought
it'd
make
a
good
good
demonstration
of
barring
slow
internet
would
have
made
a
great
demonstration.
A
And-
and
this
particular
plug-in
goes
into
the
app
finds
out
that
it's
got
two
routes
I'm,
not
sure
why
we
chose
to
show
them
and
pick
one,
but
you
know
pick
one
and
then
it
will
throw
that
up
into
the
browser,
and
so
it's
just
it's.
It
can
be
convenience
helper.
Okay!
Now
we
will
come
back
to
that
plug-in
because
it
also
helps
bring
up
service
dashboards,
but
it's
like
there's
lots
of
plugins,
there's
80
or
so,
and
they're
pretty
easy
to
write.
Should
you
wish
to
extend
your
experience
now?
A
A
Try
to
avoid
that
ending
caching,
any
disk,
any
persistence
you
want
to
do
outside
of
the
container
and
the
way
that
we
do
that
or
maybe
make
that
convenient
is
with
a
marketplace
of
services,
and
this
is
where
everyone's
Cloud
Foundry
starts
to
become
a
little
different
from
each
other,
because
it
depends
on
what
your
Cloud
Foundry
and
your
platform
team
want
to
offer
things
take
time
and
money,
especially
data.
You
know
the
moment.
You
start
writing
to
a
database.
A
You
assume
that
someone's
looking
after
it
someone
backing
it
up
someone's
going
to
provide
services,
so
they
might
not
want
to
provide
every
database
known
to
society.
They
might
just
want
one
sequel
database,
one
message,
bus,
etc.
So
the
way
we
find
out
what
we've
got
is
with
CF
Marketplace
and
unfortunately,
the
Cloud
Foundry
I'm
talking
to
actually
has
a
lot
and
that
can
take
a
little
time
to
display.
A
That
would
come
back
to
that.
But
here
is
an
example.
They
have
one
called
elephant
sequel
which
happens
to
be
Postgres.
There
are
so
different
plans.
Turtle
is
free
and
I'm
gonna,
be
honest,
I'm,
a
sucker
for
free
things,
deep
down,
there's
a
university
student
in
me
that
still
wants
free
stuff
all
the
time
and
whether
it's
a
sausage
and
bread
or
it's
a
free
database
I
mean
you
know
stickers,
whatever
all
right
and
not
only
do
they
have
a
lot
of
them.
A
They
don't
print
very
nicely,
there's
lots,
but
yours
might
only
have
a
few,
so
they
have
different
names
and
and
there's
different
vendors.
So
there's
lots
of
different
people
in
the
Cloud
Foundry
community
who
can
provide
your
platform
team
with
a
database
that
you
might
want.
So
it's
a
conversation.
This
is
where
you
go
back
to
your
platform.
Operators
say
hey:
why
don't
we
have
Postgres
Postgres
is
awesome
and
they
say
we
like
my
sequel.
You
know
anyway,
they
have
a
really
adult
conversation
like
that
want
it.
You
can't
have
it
like
children
anyway.
A
So,
let's
create
one:
let's
make
the
font
bigger,
again
crate
service,
so
little
command
create
service
and
let's
give
it
a
name
DB,
it's
a
good
name
as
any,
and
what
this
is
doing
is
it's
the
command
line
tool
saying
to
Cloud
Foundry
I
want
this
database
Cloud
Foundry
it's
plug
and
play
again.
It
goes
off
to
what's
called
a
service
broker.
A
bit
of
internal
teacher.
Something
and
the
service
broker
is,
is
has
that
abstracted
understanding
of
what
is
this
request?
A
So
there
is
like
an
elephant's
equal
service
broker
or
equivalent,
and
it
gets
the
request
and
says
goddess:
let
me
go
and
create
one
of
those
for
you.
Whatever.
That
thing
is,
in
this
case
a
elephant's.
Equal
turtle
plan
is
like
a
shared
database
on
an
existing
Postgres
cluster
I.
Think
I
didn't
write
it.
That's
just
my
understanding
of
what
they
did
so
now
it
exists,
but
we
can't
use
it
yet
because
we
haven't
got
user
name
password,
so
in
Cloud
Foundry
that's
called
binding,
so
we
bind
the
service
to
our
application,
Tony
Rudy.
A
Now
the
another
request
that
goes
from
the
command
line,
tool
to
cloud
foundry
and
Cloud,
Foundry
fords
it
onto
the
service
broker
and
the
service
broker,
takes
it
and
says
a
binding
I
can
do
that
in
Postgres.
That
means
creating
a
user,
perhaps
creating
some
roles
and
and
generating
passwords
and
then
returning
them
back
to
the
Cloud
Foundry
and
then
back
to
the
user
or
to
the
application.
Sorry,
and
and
now
it
exists.
A
So
if
I
now
restart
my
app,
you
might
think
what
exactly
there's
a
hollow
world
app
do
with
the
database,
and
that
is
an
excellent
question.
It
does
nothing
with
it.
Nothing
about
what
I
just
did
makes
an
app
know.
What
Postgres
is
so
your
application
still
needs
to
know
what
Postgres
is
how
to
talk
to
Postgres.
What
we
have
done
so
far
is
is
create
one
and
make
it
give
it
credentials
and
then
we'd
have
to
add
Postgres
support
where
happen.
A
When
we
did
push,
we
did
see
if
push
that
long
process
of
discovering
it
was
a
ruby,
build
pack
pulling
in
a
version
of
ruby,
pulling
in
version,
ruby,
gems,
falling
all
the
gems
and
everything
and
making
it
what
we
call
a
droplet,
that's
called
staging,
and
then
we
take
that's
like
a
docker
image.
So
it's
our
own
internal
interpretation
because
we
exist
longer
than
Daka
does
that's
called
a
droplet
and
then,
when
we
start
the
app,
we
basically
just
run
copies
of
that
droplet
and
so
restart
basically
says
just
take
the
last
drop.
A
It
was
good
enough
just
started
again,
but
with
new
environment
variables.
Restage
goes
back
and
says,
take
the
source
code
we
already
had
and
just
do
that
dual
pack
thing
again
and
then
restart
and
now.
The
reason
that
it
suggested
restaging
is
because
it's
more
likely
that
it
will
cover
all
edge
cases
but
pretty
much
most
apps
don't
need
restaging
just
because
some
environment
variables
changed.
A
A
A
A
Alright,
so
here
we
are
now,
this
is
all
gobbledygook
and
I'll
come
back
to
why
that's
gobbledygook
is
there.
This
is
nothing
looks,
doesn't
look
anything
like
my
app,
but
what
is
useful
right
up
front
is
the
environment,
and
this
is
all
the
different
environment
variables
that
were
provided
to
our
app
you
might
like
to
use
some
of
them
note
worthily
is
port,
that's
the
port
that
your
application
can
buy.
It
should
bind
to
in
order
to
receive
HTTP
traffic.
A
A
And
it
includes
the
URLs
that
were
bound
to
your
app,
so
that
can
be
useful,
because
sometimes
you
might
want
to
provide
those
back
to
users.
What
what
is
my
URL,
so
you
can
dynamically
look
that
up
the
one
that
we
just
looked
at
was
services.
So
how
would
we
find
what
the
their
Postgres
that
world
is
given
its
provided
through
this
vcap
services,
environment?
Variable,
which
is
this
big
JSON
object?
A
And
if
you
have
multiple
without
an
email
and
Postgres
and
an
s3
bucket
it
all
be
in
there
and
it's
your
applications
responsibility
to
look
through
this
and
find
credentials
which
we
can
see
here
and
yeah
so
anyway,
your
application
probably
do
this
in
memory,
but
JQ
is
also
on
the
filing
system.
So
you
can
sort
of
do
that
as
well,
but
your
application
and
most
languages
have
a
Cloud
Foundry
library,
that's
good
at
pausing.
A
A
This
temp
lifecycle
she'll
actually
have
it
as
a
as
a
snippet,
and
what
that
does
is
that
now
puts
us
in
their
application
anyway.
There's
blog
post
about
this,
but
that
makes
sure
that
you've
got
everything
that
your
application
expects,
but
I
feel
like
that
needs
more
introduction.
So
I
wish
I'd
never
do,
and-
and
we
talked
about
that,
I
will
just
show
one
little
example,
so
we
run
ghost
stock
of
Wayne.
We
run
ghost
as
our
blog.
A
We
run
it
on
Cloud
Foundry
in
order
to
set
it
up,
I
needed
to
take
the
bindings
that
came
in
and
create
a
JSON
file.
That
ghost
would
use
to
load
it
up
so
rather
than
fix
it
in
JavaScript
at
runtime,
I
just
generate
a
big,
and
so
we
actually
pause
this
thing
in
at
start
time.
So
there's
a
if
your
application
has
a
dot
profile
file.
A
It
is
run
before
every
container
is
wrong,
so
it's
a
great
way
to
generate
config
files,
anything
at
runtime,
so
I
mentioned
it.
As
an
example,
I
have
had
to
look
in
this
B
cap
services
run
up
through
Jake
Jake.
You
pull
at
values,
crate
config
flow
there.
We
are
look
at
creating
a
big
JSON
file,
config
father
ghost
once
rather
than
go,
modify
ghost
just
don't
run
in
Cloud
Foundry,
so
the
doc
profiles
is
a
great
solution
to
how
do
I
generate
confit
based
on
at
runtime?
And
that's
that's.
A
It
I
hope
if
you
don't
have
a
cloud
foundry
already.
These
were
each
of
these
Alice
has
a
free
plan,
or
at
least
you
can
sign
up,
possibly
with
the
exception
of
cloud
gov,
and
there
is
not
just
my
video
but
many
other
getting
started
videos,
and
if
you
have
any
questions
now
or
later,
please
please
ask
thank
you
very
much.
A
Yep
staging
that
I
appreciate
that
as
they
are
to
use
of
the
word
staging
club,
foundry
has
not
so
I
say:
staging
a
production,
okay,
good
question,
so
the
question
was
I
used
the
word
staging
twice
once
I
said:
staging
a
production,
there's
like
a
pipeline
and
later
on,
I
made
reference
to
when
we
talked
about
restaging
that
the
CF
push
does
a
staging
process.
They
are
different
uses
of
the
word
staging
and
for
that
I
apologize,
and
so
once
you
start
deploying
apps
once
you
realize
how
easy
it
is
to
point
out
once
why?
A
Wouldn't
you
just
deployed
a
second
time
and
say
well,
the
first
ones
out
one
that
always
deploy
too
and
once
we're
happy,
we
can
deploy
it
again
to
production,
and
perhaps
you
want
to
start
deploying
off
branches
and
want.
You
know
that
you
can
do
anything.
You
like
it's
so
easy
to
deploy
and
create
new
routes
and
delete
the
CF
delete
and
you
delete
an
app.
A
A
This
app
is
most
edging
out
that
one's
production
really
is
a
function
of
what
people
use
it
for
if
no
one
knows
about
staging
app,
that's
the
staging
app
the
production
app
is
the
one
people
complained
about
when
it
goes
down
and
yes,
then
I
use
staging
refer
to
the
bill
back
process.
I
apologize,
good,
pickup,
sorry
about
that
cool.
Well,
thank
you
very
much.