►
Description
GitHub Enterprise is used by some of the most respected companies in the world. Find out how to bring GitHub Enterprise to your own company.
Led by Matt Colyer, the Product Manager for the GitHub Enterprise, the talk will cover the basics of administration, what's possible and how you can get the most out of your GitHub Enterprise install.
About GitHub Universe:
Great software is more than code. GitHub Universe serves as a showcase for how people work together to solve the hard problems of developing software.
For more information on GitHub Universe, check the website:
http://githubuniverse.com
A
A
So
some
people
ask
likewise
github
Enterprise
important
and
we
really
built
get
up
enterprise
for
the
customer
who
can't
put
their
code
on
the
cloud
and
that
takes
a
lot
of
different
forms.
Some
companies
have
government
regulations.
Other
companies
have
company
policies
that
don't
allow
for
their
companies
to
put
their
code
on
line,
but
for
customers
who
can
put
it
online,
we
actually
really
recommend
get
up.
Calm,
that's
the
best
experience,
but
today
we're
gonna
be
talking
about
good
of
enterprise
for
the
companies
that
aren't
able
to
put
their
code
in
the
cloud.
A
Since
that
time,
we've
released
a
release
every
quarter,
as
you
can
see
here,
2.1,
2.2
and
2.3
with
all
the
specific
features
under
each
one
of
them,
and
one
of
the
big
themes
of
the
last
year
was
that
we
want
to
enable
customers
to
run
where
they
want
to
run
so
initially,
when
we
launched,
you
can
only
run
it
in
VMware
AWS,
and
that
was
it
over
time.
We've
added
in
other
platforms
such
as
OpenStack,
pvm,
Zen,
hyper-v
and
Azure.
A
A
An
important
user
group
to
us,
like
developers,
are
an
important
group,
but
administrators
are
as
well,
and
so
we
want
to
enable
you
to
do
your
job
better,
and
so
some
of
the
features
listed
here
are
also
about
making
administrators
lives
better
and
kind
of
the
final
piece
that
I
kind
of
want
to
highlight
is
that
we're
really
a
customer
driven
company?
We
really
do
value
your
feedback
and
the
different
channels
that
we
get
from
I
work
very
closely
with
the
support
team.
A
I
also
work
very
closely
with
our
sales
team
and
I
hear
your
stories
on
the
field
day
in
and
day
out,
and
so
some
of
these
features
might
be
a
result
of
conversations
you've
had
over
the
past
year.
So
it's
an
important
feedback
loop
that
we
want
you
to
know
that
we
really
take
your
feedback
very
seriously
so
kind
of
getting
further
into.
How
does
actually
apply
to
you
so
for
people
who
haven't
run
it
before.
A
These
are
the
platforms
that
we
support
and
the
first
big
decision
that
you
need
to
make
in
order
to
run
get
up.
Enterprise
is
to
pick
one
of
these
platforms,
and
so
Austin
companies
already
have
one
of
these
infrastructures
set
up,
and
so
they
pick
the
one
that
they're
most
familiar
with
and
then
I'm
going
to
walk
through
the
initial
configuration
of
get
up.
A
Enterprise
walk
you
through
the
different
settings
we
have
and
the
differ
capabilities
that
that
offers
you
the
plug
in
with
your
existing
infrastructure,
and
one
of
the
things
I'll
highlight
is
that
we
really
strive
for
simplicity,
and
so,
as
part
of
that,
we
offer
a
lot
of
these
administrative
tools
through
the
web
UI
which
you'll
see
here
and
it's
from
the
get-go.
As
soon
as
you
start
up
your
machine
you'll
see
this
page
and
you
can
get
started
fairly
easily.
A
So
people
who
don't
even
have
a
lot
of
administrator
experience
can
get
started
fairly
easily
and
then
the
other
big
thing
is
that
we
try
to
set
defaults.
So
if
you
actually
launched
an
enterprise
install
and
you
click
Save
and
like
set
up,
it
will
actually
just
work
out
of
box.
Of
course,
I
won't
do
exactly
what
you
want,
but
we
really
want
to
make
you
successful
from
the
get-go
so
with
that,
let's
actually
get
into
some
of
the
the
pages
here.
A
So
this
is
the
very
first
page
that
you'll
see
on
your
install
when
you
come
in,
it
has
the
license
file
which
you'll
get
you
can
either
get
a
trial
license
from
our
website
or
you
can
get
it
joyfully
from
the
sales
team
and
that
that
indicates
how
many
users,
that
instance
can
run,
and
then
you
set
an
administrator
password,
and
so
this
is
a
single
password
for
all
the
administrators
in
your
organization,
and
this
is
at
like
the
infrastructure
level.
So
it's
like
people
who
have
control
over
the
OS
and
the
file
system.
A
One
of
the
recommendations
that
we
make
is
that
we
really
strongly
encourage
companies
to
use
password
managers
and
best
password
practices
around
this,
because
this
is
really
the
keys
to
the
kingdom
on
your
install.
So
you
want
to
make
sure
that
people
who
have
access
to
the
system
are
really
trusted,
and
it's
only
those
sort
of
people
that
have
access
the
first
area
of
configuration.
A
The
next
kind
of
area
of
configuration
is
the
host
name.
So
this
is
pretty
clear
for
most
people.
It's
the
name
that
you're
going
to
give
your
enterprise
install
another
really
important
feature
here.
That
I'm,
not
sure
that
everybody
is
aware
of-
and
this
is
kind
of
a
more
advanced
feature-
is
the
subdomain
option,
and
this
is
something
that
we
introduced
in
the
2
point
0
release
as
well,
and
it
actually
turns
out
to
be
fairly
important
because
subdomain
isolation
allows
you
to
increase
the
security
of
your
install.
A
Without
this
option
turned
on
your
users
can
create
content
under
the
same
domain
that
the
application
runs
in,
which
opens
up
additional
security
vectors
that
you
might
not
want
to
open
up.
So
we
really
do
recommend
that
all
of
our
customers
run
with
this
enabled,
but
that
the
setup
is
more
complicated.
So
the
couple
caveats
there
is
that
you're
going
to
need
an
ssl
certificate
that
supports
wild
cards,
because
there's
about
10
to
15
different
subdomains
that
you're
going
to
run
over
ssl.
A
The
other
thing
that
you're
going
to
need
is
dns
records
set
up
to
each
of
these
subdomains
so
that
your
users
can
get
access
to
it.
So,
while
there
is
a
lot
of
extra
work
to
kind
of
turn
on
that
subdomain
isolation,
it
really
is
important
and
we
encourage
you
to
turn
that
on
so
just
to
highlight.
If
you
take
one
thing
away
from
that
slide,
I
want
everybody
to
remember.
You
should
really
turn
on
subdomain
isolation.
A
The
next
thing
that
we've
kind
of
found
over
time
is
that,
from
a
customer
perspective,
is
that
making
a
clear
name
as
to
what
github
is
is
super
helpful.
So
we
found
that,
like
when
people
use
github
in
the
internal
URL,
it's
much
more
clear
to
the
users.
What's
going
on
so
I
know.
Not
everyone
here
has
total
flexibility
over
what
they
name
things,
and
then
they
have.
A
A
The
next
kind
of
configuration
area
is
the
time
network
time
configuration
and
most
people
will
just
want
to
leave
this
alone.
It
usually
works
out
of
the
box.
The
only
reason
you
want
to
switch
this
is
that
if
you
have
a
specific
I'm
infrastructure
setup-
and
if
you
do-
you
probably
know
what
to
put
in
there.
A
A
A
A
The
downside
is
that,
like
I
said
it's
totally
separate
from
all
of
your
systems
and
a
lot
of
our
customers
want
to
be
able
to
integrate
single
sign-on
or
they
already
have
an
LDAP
directory.
So
those
are
the
other
options
that
we
offer.
So
ldap
is
the
next
one
that
I'll
go
over,
and
this
allows
you
to
use
like
an
active
directory
directory
to
authenticate
all
of
your
users.
You
can
specify
certain
groups
of
users
that
are
permitted,
so
maybe
you
mark
all
of
your
developers
in
a
certain
ldap
group.
A
A
Another
great
feature
that
we
introduced
in
the
2.1
series
is
that
it
allows
you
to
sync
permissions
over
four
teams.
So
if
you
already
do
a
lot
of
role
based
management
and
your
LDAP
directory,
you
can
say
like
this
team.
Like
this,
your
web
team
is
marked
by
a
certain
ldap
group.
You
can
actually
sink
that
over
into
your
enterprise,
install
so
that
you
don't
have
to
maintain
both
permission
groups.
You
can
do
all
of
your
user
administration
just
in
ldap.
A
Other
couple
of
features
that
we
have
is
you're
able
to
sync
ssh
keys,
so
ssh
keys
are
kind
of
difficult
for
developers
to
set
up
sometimes,
and
so,
if
you
already
have
those
in
your
LDAP
directory,
you
can
copy
those
over
so
that
your
users
don't
have
to,
and
you
can
keep
them
in
sync,
if
you
have
a
sage,
key
rotation
policies.
Anything
like
that.
A
So
we
have
an
extensive
developer
documentation
and
it's
all
kind
of
detailed
there
as
to
how
to
how
to
manage
that
the
next
option
is
sam'l,
and
so
Samuel
is
good,
because
it
offers
a
couple
things
that
L
Deb
doesn't
offer.
If
you
have
multiple
LDAP
directory
servers,
we
don't
support
that
with
ldap
directly.
The
best
way
to
kind
of
federated
ldap
servers
is
through
sam'l.
The
other
thing
that
same
ole
really
provides.
A
You
is
that
the
ability
to
do
single
sign-on
so
for
users,
it's
a
better
user
experience,
I'd,
say
I,
go
to
my
corporate
email
and
I
sign.
It's
a
sam'l
and
now
I
have
a
cookie
set
on
my
machine
so
that
it
knows
that
I'm
logged
in,
if
you
go
to
your
getup,
install
get
up
knows
that
you've
already
signed
in
as
in
it.
If
it
conforms
to
your
sam'l
policies
to
say
in
the
last
half
an
hour
you
signed
in
that
cookie
will
still
work
on
your
good
of
install.
A
A
The
other
thing
that
we've
found
useful
for
is
like
I,
said,
with
those
multiple
ldap
servers.
If
you're
acquiring
companies
a
lot
of
times,
companies
come
in
with
their
own
directory
sets
and
so
an
easy
way
to
kind
of
integrate.
An
acquisition
into
your
company
is
to
use
sample
to
bridge
those
to
ldap
directories
and
provide
like
a
single
interface
into
your
good
of
install.
A
Our
last
authentication
option
is
cast
which
stands
for
centralized
of
penetration
service.
It's
a
little
less
well
known
than
sam'l,
but
the
idea
is
very
similar.
It
provides
a
single
sign-on
interface
to
your
users,
I
think
most
customers
who
use
this
option
already
have
cast
set
up,
and
so
that's
why
they
continue
to
use
it
to
standardize
their
infrastructure.
A
The
next
option
is
privacy
and
security,
so
this
is
again
a
pretty
important
section.
Almost
all
of
our
customers
are
going
to
want
to
configure
this.
The
very
top
thing
there
is
the
ssl
certificate,
which
is
incredibly
pardon,
so
we
ship
with
a
generated
a
self-signed
certificate
on
the
appliance
which
is
great
to
get
started
so
that
your
initial
administration
session
is
if
encrypted.
But
you
really
need
to
replace
that
with
an
actual
ssl
certificate
that
you
own
and
trust
in
order
to
provide
that
security
to
your
users.
A
The
other
thing
that
I'll
mention
here
is
private
mode,
so
this
is
kind
of
a
big
choice,
so
some
of
our
customers
turn
it
on
and
some
of
them
turned
it
off.
Most
of
our
customers
run
behind
a
firewall,
so
they
already
limit
network
access
and
so
outside
contributors
can't
access
this
network.
So
if
you
disable
private
mode,
any
repository,
that's
public
will
be
viewable
inside
of
your
VPN
other
customers.
A
Don't
they
want
even
a
more
control
over
that
access,
and
so
they
enable
private
mode
and
so
private
mode
actually
disables
any
kind
of
access
without
an
account.
But
that
means
that
each
person
who
looks
at
a
github
page
is
going
to
have
to
have
a
validated
license
account.
So
that
includes
just
pages
and
public
repositories.
A
The
other
third
option
that
we
see
people
use
this
for
is
some
people
host
their
github
enterprise
install
on
the
public
Internet,
and
so,
if
you
do
run
it
on
the
public
Internet,
it
is
a
bigger
attack
service
and
we
definitely
require
a
private
mode
to
be
turned
on,
because
you
should
really
only
have
your
users.
Looking
at
your
install,
you
don't
want
the
general
internet
traffic
looking
at
it
a
final
option
here
at
the
bottom.
Some
of
you
might
be
excited
about
this.
This
is
a
recent
addition
in
2.3
is
HTTP
outbound
proxy
support.
A
A
This
the
pages
configuration
section,
is
very
simple:
it's
a
choice
of
whether
you
want
to
enable
pages
for
your
customers
or
not.
We
strongly
recommend
that
you
leave
this
option,
enabled
it's
enabled
by
default.
The
reason
that
we
recommend,
that
is,
that
it
allowed
like
pages,
allow
people
to
create
some
pretty
amazing
things.
The
thing
that
Chris
mentioned
earlier
in
his
keynote
talk
where
somebody
had
actually
created
starcraft
in
a
browser
and
put
it
on
pages,
uses
the
pages
product.
A
The
pages,
if
you're
not
familiar,
is
the
way
to
take
a
public
like
a
repo
and
turn
it
into
a
public
website,
and
all
you
do
is
do
a
git
push
and
it's
available
online.
So
it's
a
pretty
powerful
tool
for
people
who
don't
do
a
lot
of
web
development
that
they
can
just
get
started
fairly,
easily
use
our
github
desktop
client
and
pushed
right
click,
close
server
and
then
all
of
a
sudden
they
have
a
website,
and
then
they
can
collaborate
with
other
users
to
keep
that
site
up
to
date.
A
So
I've
seen
some
pretty
good
uses
of
this
for
public,
like
company
intranets,
allowing
people
to
distribute
information
to
other
parts
of
the
company
documentation.
So
if
you
look
at
developer
decade,
up
com
is
actually
run
on
a
page
of
site
as
well
as
help
decade
up
calm.
So
we
use
this
product
extensively
and
I
know
their
couples.
That
we
really
like
to
mention
is
reacted.
Hubzero
is
a
Facebook's
open
source
library
and
they
use
it
as
well
and
then
electron
get
a
bio
is
also
another
pages
site.
So
it's
a
really
awesome
product.
A
Some
companies
aren't
able
to
enable
it,
but
it's
pretty
useful,
featuring
the
final,
like
kind
of
most
advanced
part
of
the
settings
page
is
the
monitoring
and
logging
page.
So
you
here
you
can
configure
SNMP
servers
where
you
forward
SNMP
traffic
you
can
in
it.
You
can
also
disable
it.
If
you
don't
know
expose
that
SNMP
information,
you
can
enable
log
forwarding
for
syslog,
which
we
strongly
recommend
logs,
are
fairly
important
and
they
have
a
lot
of
data
in
them.
You
can
start
to
get
some
really
interesting
business
value
analytics
out
of
it.
A
You
can
see
which
pages
and
people
are
using
and
how
fast
they
respond
and
like
where
your
developers
are
working.
It
also,
like
I,
said,
returns
performance
data,
so
you
can
get
a
sense
of
that
as
well.
The
other
thing
you
can
do
is
you
can
proactively
monitor
if
something
isn't
right.
I,
if
you
notice
that
there's
a
lot
of
hits
to
a
single
page,
sometimes
I
mean
developers
make
mistakes.
A
The
next
important
thing
is
setting
up
alerts.
I
mean
we'll
talk
a
little
bit
more
about
this
later,
but
you
want
to
make
sure
that
you
have
your
alerts
in
place
and
you
can
do
that
through
any
of
those
three
options.
You
can
use
SNMP,
collecti
and
logging
to
be
able
to
alert
on
different
parts
of
performance
metrics
of
the
instance.
A
So
now
we're
going
to
shift
gears
a
little
bit
away
from
the
very
like
configuration
oriented
stuff
to
best
practices
across
the
entire
appliance,
and
so
one
of
the
first
areas
that
people
often
ask
about
is
high
availability
and
disaster
recovery.
Having
a
highly
available
instance
is
incredibly
important.
I,
like
a
lot
of
people's
developers,
can't
work
without
it,
and
so
we
really
recommend
a
very
specific
set
up
to
be
able
to
get
the
most
out
of
your
github
enterprise
install.
A
So
the
key
thing
is
that
enterprise
currently
supports
a
single
primary
instance
and
a
single
replica
instance,
and
you
want
to
be
able
to
make
sure
that
those
two
are
connected
with
a
high
bandwidth,
low
latency
link.
So
we
don't
typically
recommend
that
you
put
your
replica
like
halfway
around
the
world.
Like
some
people.
Do
ask
that
they're
like
oh
well.
We
want
one
server
on
one
continent
and
another
serve
on
a
different
continent,
and
we
actually
don't
recommend
that,
because
of
the
reliability
of
those
links
bandwidth
available.
A
What
instead,
we
recommend
is
that
you
run
both
your
primary
in
your
replica
instances
within
the
same
data
center,
but
on
stacks.
So
separate
power
supply
is
separate
network
routing
as
separate
as
you
can
make
it
within
the
same
data
center,
but
at
the
same
time,
providing
a
high
high
bandwidth,
low
latency
link
between
the
two
to
make
sure
that
everything
is
kept
in
sync.
And
then
another
thing
that
I'll
point
out
here
is
the
backup.
A
Utils
is
a
project
that
we
support
and
it's
our
solution
for
doing
disaster,
recoveries
that
we
allow
you
to
take
snapshots
of
your
data
and
copy
it
off-site,
and
so
for
those
customers
that
do
want
that
cross-site
guarantee.
We
recommend
that
you
actually
run
the
backup
utils
on
a
host
in
another
data
center
here,
as
illustrated
by
this
orange
box,
and
that
allows
you
that
same
kind
of
guarantee
of
having
your
data
safely
copied
to
another
geographic
region.
But
it
doesn't
come
with
the
same
performance
requirements.
A
So
kind
of
an
the
next
area
that
people
kind
of
often
asked
about
is
like
well.
So
now
I
have
a
whole
get
up
install.
How
do
I
use
organizations,
and
so
we
have
we've
seen
a
lot
of
customers
using
them
in
a
lot
of
different
ways,
and
one
of
the
things
that
we've
found
most
important
is
that
a
lot
of
people
will
just
create
a
single
organization
to
start
and
then
start
adding
everything
under
that
one
organization,
and
that
works
up
to
a
certain
point.
But
it's
probably
not
the
best
practice
like
remember
that.
A
Essentially
you
have
unlimited
organizations
and
they're
really
a
tool
for
you
to
control
how
users
are
grouped,
and
it
gives
you
another
tool
in
your
tool
set
to
make
sure
that
your
policies
match
what
you
want
them
to
be.
So
one
of
the
things
that
we
found
it
useful
for
is
to
separate
out
contractors
so
like
when
we
work
with
a
partner.
A
We
actually
create
a
separate
organization
at
github,
where
we
work
with
that
that
other
partner
company
and
the
get
of
employees
that
are
permitted
to
see
access
to
that
are
added
to
that
organization
as
well.
But
that
way
we
can
guarantee
that
they
don't
have
access
to
any
of
our
other
repositories,
whether
they're,
public
or
private,
and
our
other
organizations.
A
Another
area
that
we've
seen
them
useful
for
other
customers
is
acquisitions.
So
a
lot
of
the
times
the
acquisition
process
is
kind
of
long
and
slow
and
soul.
I
kind
of
the
first
step
is
getting
that
other
company
into
your
same
install,
but
then
putting
them
in
a
separate
organization
and
then
over
time
that
allows
you
a
path
start
to
get
them
closer
and
closer
to
the
point
where
they
can
be
grouped
in
with
the
other
parts
of
your
organization.
A
So
upgrades
are
important
and
they
happen
more
frequently
now
than
they
did
in
the
past,
and
the
reason
that
we
really
want
to
create
that
steady
cadence
is
that
we
want
to
deliver
you
the
latest
and
greatest
features
that
are
tested
from
calm
and
provide
them
to
your
users
in
a
timely
manner.
So
we
really
strongly
recommend
that
you
keep
pace
with
the
upgrades,
because
oftentimes
developers
will
see
something
on
github
com
and
then
immediately
ask
administrators
in
the
field.
When
is
this
coming
for
me?
A
And
so,
if
your
have
a
proactive
like
upgrade
plan
in
place,
you
can
get
those
latest
and
greatest
advancements
out
to
your
developers.
So
our
recommendations
here
is
that
you
actually
have
a
separate
copy
of
your
kind
of
production
infrastructure
that
you
can
run
in
kind
of
a
staging
Manor,
that
you
can
take
a
snapshot
of
your
production
and
stage
that
upgrade
so
that
you
can
time
it
out
and
plan
your
maintenance
windows
and
know
exactly
what
to
expect.
A
So,
that's
kind
of
our
best
practice
recommendation
there
on
alerting,
which
we
mentioned
previously.
One
of
the
key
things
to
plan
ahead
on
is
capacity
planning,
so
getting
a
sense
of
how
your
users
are
using
that
your
disk
usage,
that's
kind
of
the
biggest
thing
that
we
see
people
consuming
over
time.
Cpu
and
memory
are
also
important
parts,
but
those
are
things
that
are
going
to
change
slower
over
time.
The
real
growth
and
resources
around
disk
usage
and
the
other
thing
that
we
see
people
alert
around
is
500
responses.
A
So
you
can
get
that
data
from
the
access
logs
and
we
also
provide
a
monitoring
or
now
in
the
instances
that
shows
you
when
their
spikes
in
those
application
errors-
and
we
don't
see
that
happen
very
often.
But
when
we
do
writing
into
our
support,
seeing
usually
resolves
the
issue
fairly
quickly.
So
the
kind
of
the
final
thing
we'll
talk
about
here
before
questions
is
logging,
like
I,
said
numerous
times
throughout
presentation.
Logging
is
really
important.
A
There's
a
lot
of
great
data
in
that
appliance
log
stash
is
like
a
great
open
source
logging
framework
that
you
can
forward
that
to
it's
available
on
github
and
it
supports
kind
of
general
blog
processing.
So
you
can
ask
questions
that
you're
interested
in
as
well
as
set
up
alerts
in
a
timely
manner
if
it's
something
that
you
can
find
in
those
logs,
customers
have
done
some
pretty
fascinating
things.
A
A
So
the
question
was:
how
often
do
we
recommend
upgrades
like
I
said
we're
always
producing
the
latest
bug
fixes
the
latest
security
fixes.
We
try
to
put
them
out
like
the
major
releases
and,
like
you
know,
kind
of
a
quarterly
process.
If
you
can
see
in
the
last
year,
they've
been
every
three
months
patch
releases
we
do
more
frequently.
The
patch
releases
are
not
as
big
of
a
change
oftentimes.
It's
just
security
updates
or
minor
changes
in
the
code,
and
so
the
patch
releases.
A
We
really
do
recommend
if
there's
a
security
fix
in
there
to
upgrade
immediately
and
often
times
the
amount
of
change
in
there.
Otherwise
is
very
minimal.
So
it's
unless
it's
a
lower
risk
kind
of
upgrade,
whereas
the
feature
upgrades
are
like
longer
and
have
involved
more
change,
and
so
we
really
recommend
kind
of
staging
out
and
making
sure
it
works
in
your
environment.
First,
before
rolling
it
out
to
all
of
your
developers,.
A
A
Yeah,
so
we
don't
offer
a
CI
solution
as
a
hosted
version,
but
we
definitely
have
partners
today.
So
like
I
know,
Travis
was
one
of
them
who
does
and
the
recommendations
of
the
air
is
that
it's
really
crucial.
We
integrate
with
a
lot
of
different
CI
systems
like
I,
know.
Jenkins
is
another
popular
one.
You
want
to
make
sure
that
your
CI
systems
are
set
up
to
pull
or
not.
A
That's
a
pole,
sorry
to
look
for
the
web,
hooks
of
like
events
and
most
third-party
integrators
have
some
solution
for
github
that
will
receive
those
web
book
endpoints
and
builds
based
off
that
if
you're
pulling
its
introducing
additional
load
on
this
river,
that
just
doesn't
need
to
be
there
and
oftentimes.
Ci
farms
are
like
the
biggest
consumer
of
those
resources
way
in
the
back.
A
A
B
A
It
now
a
nurse,
so
the
question
is
about
the
back
of
the
tools
currently
run
sequentially.
Do
we
have
any
plans
to
make
them
parallelized
I?
Think
that's
something
we
would
definitely
be
open
to.
I
think
we've
tried
it
in
the
past
and
we
were
concerned
about
the
amount
of
load
that
it
introduced
on
the
server
it
set
to
do
that
because
it
is
like
putting
load
on
the
server
you're
pulling
from,
but
it's
definitely
something
that
I
can
see
us
adding
in
the
future.
A
So
currently
today
is
not
automated.
That
was
a
very
intentional
decision.
What
we
do
provide
is
that
we
want
to
make
very
clear,
like
once,
you
decided.
The
hard
part
is
deciding
when
to
failover
quote
unquote,
it's
hard
for
us
to
determine
as
like
an
automated
piece
of
software
when
something's
failed,
but
what
we
do
provide
is
a
way
that
it's
fairly
easy
to
go
into
a
replica.
A
It's
like
I
think
two
or
three
button
clicks
in
like
less
than
a
minute
to
configure
the
replica
to
act
as
a
primary,
but
the
actual
DNS
failover,
the
like,
where
you
swing
a
record
from
your
primary
or
replica,
is
going
to
be
up
to
your
infrastructure
and
the
timing
around
that
again
is
going
to
be
your
TTL
on
your
DNS
record.
So
today
none
of
that
is
automatic
because
we
think
it's
important
that
customers
make.
That
decision
has
to
blend
a
failover.
A
Otherwise,
you
get
into
situations
where,
if
we
fail
over
too
quickly-
and
it
didn't
actually
take
for
all
of
your
users
now
you
have
data,
that's
up
to
date,
them
both
and
now
you
have
a
tougher
problem
of
resolving,
which
is
the
source
of
truth.
So
that's
the
reason
for
not
having
a
totally
automated
hia
set
up.
A
Don't
provide
any
tooling
today
to
allow
import
from
other
code
systems.
We
do
have
that
migrator.
That
allows
you
to
move
between
installs.
We
have
some
open
source
ruling.
We
can
definitely
point
you
at
on
that,
and
we
also
have
a
services
team
that
does
this
on
a
pretty
regular
basis.
So
they've
got
some
pretty
good
practices
around
that
as
well.
A
Oh
right,
yes
forgot!
Yes,
so
we
actually
have
the
services
team
on
the
generalist
generously
offered
to
have
a
30-minute
kind
of
like
check
in
session
with
each
customer
who's
interested.
We
have
a
limited
number
of
spots,
but
you
can
definitely
check
in
with
them
they're
in
the
back
left
corner
over
here.