►
Description
Depoloying, Managing and Updating Wordpress (or Drupal) in an .EDU environment can be daunting. OpenShift Commons .EDU SIG Chair Stephen Braswell (UNC) talks about how they are doing it at UNC and a lively discussion follows with insights shared from McMasters, UMIch and others.
A
What
we
did
so
we
have
on
our
campus
kind
of
an
on-premise
software
as-a-service
WordPress
environment.
We
have
two
of
them
actually
once
kind
of
individuals
in
one
more
departments.
That's
generally
and
that's
not
running
up
the
shift.
Currently,
that's
just
for
other
reasons,
not
really
technical
reasons.
A
We
tend
to
push
people
towards
those
if
they
can,
because
there
is
a
group
that
maintains
and
supports
that
for
them
there
are
cases
where
someone
already
has
an
existing
WordPress
sites
and
doesn't
want
to
do
manage
to
necessarily
the
server
anymore,
but
they
don't
want
to
use
the
sass
offering
because
they
have
plugins
that
they
want
to
use
that
the
support
team
doesn't
to
support
things
like
that.
So
then
they
might
stay
and
have
WordPress
on
our
open,
shipped
environment,
and
so
we
are,
we've
been
allowing
people
to
this.
A
So
we've
been
on
the
shift
since
version
2
and
in
the
version
2
days
that
QuickStart,
so
we
had
WordPress
quick
starts
so
that
people
would
quickly
stand
up.
Wordpress
they'd
have
to
worry
about.
You
know,
understanding
they
need
to
set.
The
database
need
to
setup
all
this
and
that
so
we
made
it
very
simple
for
them
and
when
we
migrated
to
a
bishop
version
3,
we
just
simulated
what
we
had
with
the
quick
starts
and
templates
to
make
it
easier
for
people
to
start
WordPress
environments.
A
We
also
have
people
that
that
do
the
same
for
Drupal.
Today
we
talk
about
WordPress,
but
everything
that
we
say
basically
the
same
for
Drupal,
except
that
you're
using
the
Drupal
code
and
the
Drupal
tools.
So
today,
we'll
talk
about
WordPress
on
my
screen.
I
have
our
git
repository
for
what
we
use
for
building
our
templates
and
images.
Basically,
what
we
have
is
we
have
a
docker
file
that
we
used
to
build
a
WordPress
image
and
stored
in
the
EM
shipped
registry.
A
It's
identifying
those
kinds
of
things
and
I'm
installing
the
WP
CLI
tools
if
it
was
Drupal
with
being
stalling,
drush
and
then
has
a
bunch
of
scripts
that
a
former
colleague
of
ours
put
together
to
to
make
getting
all
this
set
up,
pretty
easy.
So
now,
I'm
gonna
go
back
and
then
look
at
just
one
of
the
scripts,
and
this
is
the
main
one
that
does
the
heavy
lifting.
So
it
sets
up
a
bunch
of
environment
variables
which
is
in
uses
the
env
stuff
command
to
change.
A
The
various
configuration
files
sets
up
a
few
other
things
for
patchy.
Again,
we're
just
doing
this
since
when
the
container
starts
up
the
the
customer
can't
change
these
and
we're
sitting
up
so
that
it's
going
to
be
somewhat
performance
for
them
and
a
few
other
things,
and
one
of
the
big
things
that
does
the
very
end
here
is
depending
on
the
type
of
install
they
did,
particularly
for
multi-site.
A
It
uses
the
W
PCI
to
download,
install
WordPress
for
them,
and
that
happens
on
the
initial
install
there's
some
code
earlier
on
that
says,
though,
if
it's
already
recognized
it
as
a
wordpress
installed,
it's
not
going
to
try
and
stall
it
again.
So
again
we
have
a
Jenkins
job
that
builds
these
images
and
push
them
to
the
to
the
internal
of
the
shift
registry.
A
And
then
the
fun
part
happens,
and
one
switch
over
here
goes
a
little
easier
to
read:
is
our
our
up
and
shift
template,
so
I'm
not
gonna,
go
through
again
the
entire
template.
Basically,
it
sets
up
the
peach
PE
and
so
that
the
database
server
the
passwords
and
that
stuff
and
then,
at
the
very
end
we
have
a
I
guess.
There's
some
day
we
have
a
bunch
of
questions.
A
A
Don't
know
an
hour
web
console
all
of
our
custom
templates.
We
have
this
UNC
tab
and
while
all
this
show
up-
and
one
thing
I
forgot
to
mention-
we
do
have
two
types
of
WordPress
installs.
We
have
what
we
call
the
standalone,
which
is
a
PVC
base.
So
if
someone
once
basically
a
like,
they
don't
want
to
manage
the
WordPress
code.
They
do
this
and
then
the
WordPress
gets
installed
in
a
persistent
volume.
Then
they
can
go
into
the
admin,
interface
and
click.
A
The
buttons
say:
ok
update
my
plugins
update
the
version
of
WordPress
all
that
stuff,
so
that
they
can
do
they
can
do
it
as
simple
as
possible.
Those
are
people
that
want
to
actually
manage
some
aspects
of
WordPress,
maybe
they're
writing
their
own
plugins
if
they
want
to
manage
the
plug-in
separately,
for
whatever
reason
we
have
that
where
it
sets
up
so
that
it'll
do
a
basic
install
for
them,
but
then
the
code
is
managed
through
get
rather
than
just
installed
on
the
PVC.
So
we
do
the
same
thing
for
Drupal.
A
We
provide
our
customers
with
a
few
options
depending
on
their
needs.
So
if,
if
they
just
need
a
simple
WordPress
and
want
to
manage
very
little
of
it
and
push
buttons
to
update
it,
they'll
use
the
standalone
which
we
call
the
PVC
one
or
they
want
to
do
more.
Managing
they'll
use
the
git
base
one,
but
we
just
quickly
walk
through.
Just
one
show
all
those
questions
at
the
end:
here's
where
they
can
answer
all
those
questions,
and
then
we
provide
an
some
default
values
and
some
things
like
username
and
passwords.
A
They
don't
need
to
fill
in
we're
using
the
little
simple
reg
X
that
is
provided
in
templating
to
automatically
generate
those.
And
if
you
were
to
create
one,
it
would
show
you
those
when
the
the
page
closed
and
additionally,
we
have
in
this
git
repository.
We
have
a
description,
a
readme
with
the
description
of
of
what
other
fields
do
in
the
template,
but
we
also
have
custom
customer
facing
documentation
on
our
knowledgebase
site
that
kind
of
walks
them
through
some
of
the
basics.
This
they
do.
A
A
Updated
documentation,
another
thing
that
we
do
offer
that's
kind
of
new
ish
is,
we
do
have
giblet
proxies
and
a
wordpress
ship
with
plugin
that
a
former
employee
of
ours
wrote
a
plugin
for
wordpress
so
that
you
can
integrate
job
within
the
wordpress.
It
works
well
enough
for
what
our
customers
need.
We
can
provide
more
information
later
on
and
on,
and
that
would
take
a
little
more
time
to
go
into
if
others
are
interested.
A
One
of
the
challenges
which
we
mentioned
on
a
previous
call
for
us
is
getting
customers
to
maintain
and
update
WordPress
again
with
the
the
QuickStart,
the
standalone
quickstarts.
You
know
they
can
easily
get
a
notification
when
they
log
in
says.
Oh
there's,
a
new
version
of
WordPress,
this
new
version,
these
plugins
click
this
button
and
update
it,
the
people
that
are
using
the
get
based
one
it's
a
little
more
difficult
because
they
need
to
actually
go
and
commit
the
updates
themselves.
A
There's
been
a
challenge
for
making
sure
people
who
are
updating
it
when
they
sign
up
for
our
open
shift
service,
they
do
have
to
agree
to
a
Terms
of
Service,
saying
that
they
will
maintain.
Like
regardless
of
whether
it's
WordPress
or
not,
they
will
update
their
code,
they
will
maintain
that
the
security
vulnerability
and
whatever
programming
language
and
whatever
frameworks
are
they're
using
in
their
program
I
think
it
just
comes
out.
They
were
responsible
for
updating
it.
A
We
are
trying
to
figure
out
how
we
would
put
together
some
ways
to
notify
those
who
are
horribly
out-of-date
and
we're
still
investigating
some
of
that.
One
of
the
things
that
we've
put
together
is
we
put,
we
gather
some
kind
of
KPI
data
and
we're
pumping
into
log
files
and
having
someone
consume
it,
and
we
have
these
kinds
of
dashboards
that
are
shows
this
information.
So
their
example.
Over
on
the
right
hand,
side
we
see
the
templates
that
we've
created
in
some
of
them
are
the
ones
that
read
that
provides
with
every
shift.
A
A
Then
we'll
do
that,
and
this
is
a
very
crude
version.
But
I
was
doing.
Is
it's
connecting
to
a
pod
and
they're
in
exact
and
then
grepping
in
the
appropriate
file
to
pull
the
data
and
we'll
make
that
prettier
once
we
start
putting
into
the
file.
But
that
was
just
a
quick
example:
I
wanted
to
show
what
we're
doing
and
so
I
ran
through
that
a
lot
faster
than
I
thought.
A
A
So
they
can
have
access
through
the
OCR
a
state's
command
ever
through
the
terminal
tab
and
if
it's
just
web
console
and
they
have
access,
if
they're,
storing
a
persistent
bar
and
they
have
access
it
to
it.
That
way,
but
that's
that's
the
limit
they
have
and
our
other
task-based
WordPress
environments.
They
do
not
get
any
access
except
web
access
through
the
WordPress
environment,
the
web,
the
WordPress
of
web
interface.
B
A
A
A
That's
interesting,
Chris
I'd
like
to
talk
to
you
about
that
again,
a
former
colleague
of
ours
that
most
of
this
up
to
when
we
were
doing
our
conversion
from
two
to
three
and
and
we're
happy
to
to
hear
other
ideas
about
how
to
make
improvements
of
it
again.
Some
of
the
updating
of
of
WordPress
has
been
recently
just
because
we've
been
looking
more
into
some
of
the
statistics
and
doing
looking
into
options
for
container
security
scanning
and
stuff.
You
know
how
do
we,
how
do
we
identify
anybody?
A
C
There
is
that,
as
far
as
our
customers
go,
the
WordPress
sites
that
they
end
up
setting
up
are
all
gonna
be
vastly
different.
So
some
people
end
up
wanting
to
actually
customize
the
code
behind
it
itself
right,
and
so
we
can't
kind
of
blanket
the
overrides
that,
because
then
we'd
be
basically
effectively
overriding
any
changes.
D
C
Made
I
know
that's
supposed
to
be
kind
of
the
priority
behind
the
get
based
ones
so
that
they
can
actually
use
git
to
manage
their
code.
Unfortunately,
customers
use
what
you
give
them
and
they
don't
necessarily
all
do
that,
and
so
that's
kind
of
the
trick
as
term
far
as
updating
and
also
if
we
were
to
you,
know,
force
upgrade
of
WordPress
and
you
know
plugins
and
go
out
of
date
or
pausing,
stop
working,
working,
etc,
etc.
C
There's
kind
of
a
struggle
there
with
the
customers,
and
so
we
actually
have
a
kind
of
a
policy
as
far
as
using
our
platform
that
the
customer
is
technically
responsible
for
patching
their
own
applications
and
we
do
want
to
be
involved
as
far
as
alerting
them
to
this.
But
at
the
end
of
the
day,
it
is
their
responsibility
as
their
application.
A
And
one
other
thing
is
that
another
thing
we've
been
dealing
with
is
not
just
with
WordPress,
but
what
versions
of
PHP
are
they
using,
for
example,
PHP,
5.6
and
7.0
end-of-life
is
entered
the
calendar
year,
and
how
do
we
get
people
to
migrate?
Ok,
WordPress
will
migrate.
Fine,
but
maybe
the
plugin
that
they
heavily
depend
on
is
I,
don't
know
it's
still
using
something
from
five
just
six
or
something
like
that
and
and
those
have
been
challenges
as
well
as
how
do
we
identify
those
get
as
customers
to
migrate
and
such
so
I?
E
Hey
guys,
this
is
Chris
again
one
question
that
was
too
long
to
type
into
chat
for
the
first
of
all.
Thank
you
for
this
overview.
It's
great
it's
right
where
we
are
well
we're
you're
ahead
of
us,
so
it's
really
timely
for
your
gate.
Based
customers.
Are
they?
Are
they
forking
your
repo
and
making
changes
to
it?
How
how
is
their
code
integrated
into
this
into
the
site,
or
is
that
something
that
you're
doing
by
the
template?
I.
A
C
Yes,
there's
a
template
set
of
things
like
because
they're
also
using
databases
on
the
platform
to
write,
so
that
simply
goes
ahead
and
sets
up
I
WG
config
and
whatnot
to
actually
connect
to
databases.
The
way
that
open
shipped
expects
them
to
that
way.
The
customer
doesn't
have
to
have
the
knowledge
there
to
in
order
to
do
that,
and
then,
from
that
point
on
they're
effectively
managing
a
repo.
A
One
thing
I
forgot
to
mention:
I've
already
done
this
for
the
other
people,
if
you
are
get
repositories,
is,
is
restricted
to
our
campus
network.
But
if
anybody
wants
copies
of
our
of
the
shift
templates
I'm
happy
to
provide
them
to
you
and
I
mean,
obviously
you
can
have
to
use
them,
but
you're
welcome
to
see
what
we
did
and
ask
questions
about.
Why
we
did
it.
C
F
D
I
was
gonna
type
some
of
this,
but
we'll
just
come
off
mute
for
a
second
I
played
around
with
a
little
bit.
It
does
have
a
good
option
as
well,
but
they
take
a
bit
of
a
perhaps
different
approach
from
the
limited
exposure.
I've
had
the
stuff,
they
don't
fork,
but
they
don't
include
all
of
the
WordPress
software.
They
just
include
a
directory
for
templates
for
themes,
plugins
that
type
of
thing
and
merge
it
in
during
the
build.
D
E
So
when
one
thought
here,
Michigan
that
we
we're
developing
is
the
idea
of
maybe
an
80%
use
case
and
then
a
20%
use
case
where,
for
those
people
that
that
don't
have
particularly
on
the
Drupal
side,
if
they
don't
have
any
custom
modules
or
themes,
we
provide
a
base
for
them.
Where
the
themes
and
modules
are
stored.
E
In
a
persistent
volume,
we
would
update
Drupal
core
via
the
base
layer
and
then
have
all
the
pods
and
hair
at
that
base
layer
and
then
and
then
use
brush
to
update
the
module
and
then
for
those
people
that
are
doing
completely
custom
stuff
have
a
different
model,
but
I
don't
think
we
have
reached
a
real
good
agreement
as
to
what
that
model
is,
and
maybe
it's
what
you
guys
are
talking
about
where,
if
you're
on
the
20%,
you
have
the
technical
capability
to
assume
responsibility
for
all.
Your
updates
yourself,
Oh.
A
Yeah
I
think
for
us
mostly
we,
if
people
doing
custom
stuff,
they'll,
just
upgraded,
updated
to
their
git
repository
from
the
start,
and
if
people
aren't
using
anything
special
plugins,
then
then
they
use
our
kind
of
sass.
Offering
is
what
we
direct
them
to,
because
there's
a
support
team
behind
that
to
give
provide
support
on
the
plugins
and
stuff
are
actually
being
kicked
out
of
our
conference
room.
So
we
have
to
take
off
30
all.