►
From YouTube: CHAOSS Augur Meeting - 11-12-20
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
we
did
just
do
a
major
release
of
auger
and
inside
that
major
inside
that
major
release
are
a
couple
of
big
improvements
to
the
way
that
we
install
auger.
So.
A
B
A
So
what
we
did
is
just
created
our
virtual
environment
and
cloned
auger
into
a
directory
activated.
The
virtual.
A
Environment
and
so
the
way
that
you
would
the
way
that
I
install
auger,
you
can
install
auger
for
a
production
environment
like
if
you
just
got
a
server
and
you're
running
it.
You
can
just
do
make
install
and
if
you
do
make
install
you,
you
end
up
with
your
auger
dot
configuration
auger.json
in
your
home
directory
under
a
dot
auger
directory.
A
A
It's
going
gonna
ask
you
a
whole
bunch
of
it'll,
first
install
a
bunch
of
libraries
and,
what's
what's
coming
down
the
pipe
with
auger
while
this
runs,
is
we
have
a
machine
learning
branch
that
includes
a
clustering
worker
that
groups
repositories
that
have
similar
conversations
with
each
other?
It
also.
We
also
have
a
message:
analysis
worker,
that
clusters
messages
within
a
repository
and
a
pull
request;
analysis
worker
that
does
predictive
analysis
on
the
likelihood
of
a
pull
request
being
merged
into
a
repo
based
on
quantitative
statistics
of
the
history
of
of
that
repo.
A
A
A
Port
5433,
instead
of
the
default,
there's
a
number
of
reasons
for
that.
Most
of
them
amount
to
ubuntu,
always
having
an
earlier
version
that
I
want
of
postgres
installed
and
me
being
too
lazy
to
go
through
the
trouble
of.
A
You
know
uninstalling
and
reinstalling
or
changing
the
port,
and
then
you
take
a
git
lab
api
key
which
you
know.
I
guess
I'm
giving
them
away
here.
But
you
know
what,
if
somebody
wants
to
steal
these
keys,
I
can
get
another
one
so
and
then
existing
directory
or
new
directory
usually
go
with
your
directory,
and
I
have
I
have
a
home
shop,
repos
directory
that
I
use
for.
A
And
it
spins
up
all
the
things
running
running
through
your
database,
so
the
yeah,
the
machine
learning
workers
that
are
coming
are
pretty
exciting.
I've
also
got
some
students
working
on
new
versions
of
the
auger
front
end
and
we
are
getting
close
to
releasing
the
a
set
of
apis
that
allow
you
to
just
hit
them
and
get
auger
community
reports
directly
from
the
api
in
a
in
the
form
of
a
png
file.
A
So
all
you
need
to
know
is
your
repo
id
and
you
can
go
to
town
and
we're
pretty
excited
about
that
pretty
cool
yeah.
Obviously,
we
still
have
our
licensing
worker,
which
is
a
distinct
analysis,
and
we're
also
doing
some
work
on
the
slackbot
to
make
that
a
little
bit
easier
for
people
to
understand
how
to
configure
and
carter
has
done.
A
great
deal
of
work
on
documentation.
B
A
We
also
have
a
log
analyzer
that
someone
from
vmware
has
a
pull
request
open
for
that
is
going
to
get
merged
very
soon,
so
that
there'll
be
a
standard
logging
architecture.
So
you
can
see
what's
running
on
your
auger
instance
and
what's
not
anytime,
you
install
auger,
because
we're
using
node.js
you'll
get
a
series
of
errors,
and
as
long
as
it
succeeds,
you
can
ignore
them.
B
Oh
hey,
the
other
thing
I
noticed
is
that
the
the
auger
front
end
doesn't
seem
to
work
anymore.
A
B
B
A
So
if
we
were
to
run
this
instance,
it
would
be
no.
This
is
all
in
documentation
which
can
be
found
at.
A
A
And,
of
course,
these
are
your
regular,
regular
steps
so
to
run
it,
it's
just
no
hub
auger,
it
used
to
be
auger
run
and
we've
changed
it
to
auger
back
in
start,
because
that
makes
it
more.
We
just
think
that's
an
easier,
it's
more
standard
command
language
and
you
can
output
it
to
no
hub
or
whatever.
I
always
do
the
log
directory,
shawn.log
and
oops.
A
B
A
A
series
of
ports,
so,
if
you're
running
more
than
one
auger
instance,
for
example,
you're
going
to
want
to
change
the
port
and
for
the
main
server
and
then
each
of
the
workers
also
has
their
own
port
number.
So
for
if
you're
only
running
one
instance
of
auger,
you
can
just
leave
all
of
the
defaults.
A
But
if
you're
not
running,
if
you're
running
multiple
instances
of
auger,
you
just
want
to
have
obviously
each
of
the
workers
on
distinct
ports.
You
can
also
accelerate
collection
with
auger
by
having
multiple
workers
in
each
case
except
facade,
and
we
recommend
basically
the
defaults
that
we
have
are
what
we
recommend
for
the
first
run
and
it'll
go
through
your
commits
your
pull,
requests
your
issues
and
then
on
after
it's
collected
all
that
stuff.
That's
when
we
recommend
turning
on
the
contributor
worker.
B
A
A
B
A
So
the
you
know
really.
The
issue
was
that
the
contributor
worker
was
having
to
do
a
lot
of
full
table
scans
and
we
were
working
on.
We
were
focusing
on
working
software
that
works
just
fine
with
samples
like
the
chaos
organization
and
when
you
turn
it
on
3000
repos
chokes
a
little
bit.
So
we
we've
optimized,
we've
added
a
number
of
indexes
that
have
like
remarkably
improved
performance.
I've
I've
been
through
a
collection
of
7
000
repos
with
the
contributor
worker
at
this
point
so
and
so
that's
exciting.
A
But
when
it
comes
to
the
rest
of
the
configuration,
let
me
let
me
go
and
make
the
let
me
go
fix
the
make
it
vmware
make
the
vmware
server,
because
there's
an
extra
step
involved
in
in
doing
that.
So
I'm
going
to
go.
A
A
Its
ip
address,
so
here's
the
ip
address,
I'm
going
to
change
where
there
is
a
there,
is
a
vmware.
Actually,
I
might
have
it
pointed
already
to
the
new
server,
but
I'm
just
gonna
not
disclose
all
of
the
domains
on
the
recording
and
switch
over
to
my
screen.
That's
not
shared.
B
A
Is
entirely
incorrect,
all
right
so
I've
I've
moved
vmware
over
and
so
now
I'm
going
to
go
to
the
github
environment.
And
yes,
this
is
just
my
structure.
You
don't
have
to
structure
it
this
way,
but
I
keep
track
of.
I
work
with
a
lot
of
github,
orgs
and
repos,
and
it's
just
easier
for
me
in
most
cases
for
me
to
keep
them
underneath.
I.
B
B
Oh
okay,.
A
Know
yeah
I'll
have
to
go
back
in
and
fix
that.
So
this
is
your
server
and
the
key
is
for
the
front
end.
There's
one
thing:
you
need
to
change
in
augur
when
you
have
a
domain
resolution,
and
this
is
for
nginx.
B
A
And
and
I'm
just
going
to
copy
the
config,
so
I
don't
have
to
remember
everything
and
bring
it
back
over
here:
sudo
vmware,
dot,
oss
health.
I
o.
A
A
Nobody
has
to
know
that
vmware.os
has
helped
that
io
is
behind
an
auger
pivotal
and
what
we'll
do
then
is
we'll
build
the
distribution.
So
you
have
to
compile
all
the
npm
stuff
into.
A
So
then
I
just
do
a
pseudo
nginx
dash
t
to
make
sure
I
did
it
right
and
I
do
a
pseudo
engine
x
restart
and
then
I
have
to
go
back
to.
A
I'm
going
to
install
first,
you
have
to
install
the
mpm
stuff,
because
not
everybody
runs
a
website
off
of
it.
Now
our
front
end
is
not
I'm
not
going
to
pretend
our
front
end.
Is
this
giant
innovation
space
for
human
computer
interaction
right
now
and
a
lot
of
people
run
augur
without
and
it
looks
like
actually
actually
it
looks
like
I
already
did
a
run.
I
built
the
distribution,
so
I'm
just
gonna
go
to
vmware
dot,
oss
health,
not
io,
and
see.
If
it's
there.
B
B
A
This
is
obviously
from
here
for
me
too.
So
every
time
I
set
up
a
brand
new
server,
there's
this
one
little
b,
there's
this
one
little
engine
next
step,
which.
A
B
B
A
A
A
B
A
And
welcome
to
the
real
life
troubleshooting
engine
x,
configuration.
B
B
A
What
I
forgot
was
that
on
this
server
I've,
so
the
server
that
you
got
originally
was
one
of
our
very
first
servers,
and
I
just
did
the
auger
instance
name
without
putting
chaos.
B
A
B
A
B
B
B
A
So
auger
util
init
front
end.
A
A
A
A
A
I
can't
get
chrome
to
work
there,
we
go
it.
I
had
to
get
rid
of
my
cached
data
from
before.
Agar
does
cache
a
lot
of
data,
so
I
use
chrome
for
testing
a
lot
of
times
just
to
clear
my
cache.
But
now
you
can
see
that
vmware.os
health.io
is
all
up
and
running
sweet
and
has
all
your
stuff
there's
some
front
end
work
that
we
still
have
to
do
it.
A
It
doesn't
it's
not
as
fast
and
responsive,
and
there
are
some
things
with
webpack
that
we
know
we
need
to
do
to
speed
that
up.
But
honestly,
I
don't
think,
like
most
people
are
using
using
auger
for
smaller
scale.
A
Examination
of
the
people
who
are
really
like
collecting
a
lot
of
repos
are
are
doing
so
they're
using
like
auger
community
reports
or
they're
writing
their
own
queries
or
they're,
hitting
the
api
endpoints.
A
Yeah
this
this,
I
have
an
issue
open
for
somebody
to
please
please,
please,
please
like
go
through
and
do
all
the
optimizations
that
are
necessary
on
our
front
end.
A
A
But
it
does
have
about
56
license
coverage,
not
bad
from
what
I've
seen
not
a
lot
of
issues
or
any
it
looks
like.
But
it's
like
you
dumped
the
code,
and
that
was
the
end
of
it.
But.
B
A
Yeah,
understandable
yeah,
so
that's
that's,
basically
the
full
configuration
of
auger
and
the
I
there
was
one
other
thing
I
thought
I
was
going
to
show,
but
I
can't
remember
what
it
is
right
now.
A
You
can
compare
it
to
other
repos,
but
that's
been
there
for
a
long
time.
I
just
don't
know
if
everyone's
aware
of
the
awesomeness
of
what
we
have
so
you
can,
because
there
are
no
issues
in
the
smaller
repository
you'll,
see
arcanist
code
changes
pretty
high
and
looks
like
some
development
has
stopped
and
then
actually
gemfirex
oss.
These
code
line
changes
seem
to
begin
right
at
the
same
time
that
this
project
ends.
A
Oddly,
who
can
you
can
explain
that
it
looks
like
there
weren't
a
whole
lot
of
prs
run
against
this
bitnami
arcanist
repo?
This
could
be
a.
This
could
also
be
an
archive
repo.
A
For
all
I
know,
but
yeah-
and
I
don't
know-
I
don't
think
I've
run
the
insight
worker
yet
so
I
don't
think
we
have
any
insights
for
you.
Oh
we
did.
We
ran
it,
so
you
have
some
insights
that
you
can
get
and
you
can
also
sign
up
for
push
notifications
at
augie
once
I
release
the
next
version
of
that.
So
these
are.
These
are
all
the
exciting
things
happening
with
auger.
Thank
you
for
joining
joining
our
call.
Today.