►
From YouTube: Backdrop CMS - VUG - Command Line Tools
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
I
don't
know
how
to
prevent
this
from
happening
there.
We
go
um
today
welcome
to
our
uh
virtual
user
group
for
backup
cms.
Today's
topic
is
command
line
tools.
um
There's
a
lot
of
interest
in
this
topic.
This
is
pretty
close
to
our
best
attended
virtual
user
group.
I
think
we've
had
about
this
many
uh
once
before,
usually
we're
a
little
bit
smaller
than
this,
but
so
thanks
everybody
for
coming,
uh
because
we're
a
little
large
group,
let's
kind
of
do
a
quick
round
of
introductions
for
those
who
are
available
um
yeah.
A
I
think
we're
going
to
do
what
we
do
at
our
regular
meetings,
which
is
um
introduce
yourself
uh
quickly
and
then
call
on
somebody
else
that
hasn't
been
introduced.
Yet,
if
you
don't
want
to
do
an
introduction,
you
can
just
uh
either
shake
your
head
wave
us
past
or
or
not
reply
uh
I
know
luke
is,
is
busy
lurking,
so
we
won't
call
on
him
other
than
what
we
just
did.
My
name
is
tim.
A
B
A
A
C
D
Hi,
I'm
martin,
I'm
in
the
uk
um
I've
been
doing
drupal
7
for
a
while.
I
bit
my
toe
in
the
water
of
uh
drupal
uh
eight,
but
uh
I
just
couldn't
uh
uh
get
the
hang
of
it.
I
was
all
right
with
um
drush
and
used
to
doing
that
over
uh
putty.
I've
been
looking
at
backdrop
for
a
couple
of
months
now,
um
I'd
like
to
learn,
um
learn
about
the
console
tools
for
backdrop.
A
F
G
H
H
I
A
Well,
I
think
you're,
the
last
one
luke
is
not
available
to
introduce
himself,
but
I
think
a
lot
of
us
know
luke
from
his
involvement
in
the
community.
um
So
we,
the
the
the
intent
of
the
discussion,
is.
I
know
I
hear
from
a
lot
of
people
that
they're
confused
about
the
command
line
tools
in
backdrop,
because
we
have
a
couple
of
them
out
there.
A
Personally,
I've
used
brush
a
little
bit
um
and
that's
it
and
I
you
know-
and
I've
only
been
using
brush
to
a
limited
extent.
um
You
know
mostly
to
do
command
uli
to
log
into
sites
is
the
biggest
thing
I
do
with
dress
part,
some
of
the
other
things
that
I'd
like
to
do
with
rush.
I
don't
know
if
they're
working
with
backdrop
I
downloaded
b
and
installed
it
for
the
first
time
and
kind
of
got
it
working
about
a
week
ago,
I'm
still
looking
forward
to
where
that's
going
to
go
but
anyways.
B
No
not
used
to
this
kind
of
online
events
uh
still
learning
how
to
use
zoom.
So
um
we
uh
came
up
uh
with
forking
uh
prayer,
uh
composer,
uh
pray,
everything
uh
you
know
when,
when
drupal
uh
seven
went
into
two
complicated
waters,
you
know
we
decided
to
find
the
latest
um
brush
or
the
the
latest
brush
that
was
able
to
work
without
all
those.
B
uh
You
know
additional
uh
layers
of
complexity
that
it
became
later,
so
we
found
that
I
think
it
was
version
4
6,
and
we
basically
uh
when
we
say
we
it's
several
people
in
outer
grey
team.
We
just
forked
rush
and
made
it
working
with
backdrop.
Basically
uh
it
is
uh
rush,
uh
uh
4.7
or
six,
I'm
not
exactly
sure,
and
uh
we
just
replaced.
We
just
used.
B
You
know
finding
uh
replace
command
and,
of
course
we
changed
uh
lots
of
uh
passes
uh
to
make
it
work
and
now
brush
is
able
to
uh
do
everything
uh
that
uh
you
know
uh
what
brush
can
do
everything
that
dash
can
do
for
drupal
7,
basically
uh
pull
uh
the
project
from
uh
github
and
uh
uh
do
uh
all
the
uh
sync
work.
What
was
we're
missing?
Why
we,
one
of
the
reasons
why
we
decided
to
go
forward.
B
Forking
uh
drush
was
the
the
fact
that
both
b
and
um
drastic
integration
for
um
backdrop
uh
were
not
able
to
sync
the
databases
at
the
time,
I'm
not
sure
how
it
is.
Now
I
I
was
told
that
the
database
thinking
is
already
working
for
b
I
haven't
tried,
but
that
that
was
one
of
the
main
features
we
were
missing
so
basically,
when
we
uh
copied
uh
rush
and
replaced
all
the
passes
in
gave
it
a
try,
it
was
working.
uh
Most
of
the
comments
were
working,
um
but
we
never
touched
uh
since
then
rarely.
B
B
B
A
G
G
A
C
Yeah
um
so,
as
jeff
said,
he
was
the
one
that
originally
wrote
um
b
or
the
backdrop
console
and
he
wrote
it
from
scratch
for
backdrop.
So
if
you
look
at
the
original
commits
it's
just
literally
like
I
think
the
page,
clearing
or
chrome
running
command
or
something
was
one
of
the
first
ones
and
just
built
out
commands
from
there.
um
When
I
came
onto
the
scene,
I
was
I've
been
using
trush
for
years
with
drupal
and
then
with
backdrop
as
well.
C
I
was
using
that
and
it
got
to
a
point,
I'm
a
very
heavy
user
of
multi-site
functionality
in
both
drupal
and
backdrop,
and
I
was
running
a
command
from
a
multi-site
trying
to
download
a
module
into
my
site.
Specific
directory
and
crush
was
downloaded
into
the
main
directory
for
all
my
sites
to
use-
and
I
didn't
want
that.
So
I
went
and
posted
an
issue
in
the
josh's
queue
and
jeff
said
he's
accepting
pull
requests.
C
I
went
and
tried
to
do
a
pull
request
to
sort
of
fix
that
and
make
it
work
properly
with
multi-sites,
but
the
code
was
just
too
complex
for
me.
I
just
couldn't
get
my
head
around.
I
couldn't
end
up
getting
it
working.
I
think
jeff
himself.
You
can
correct
me
if
I'm
wrong,
but
I
don't
think
he
used
multi-site
much
together,
help
knowing
how
that
works.
So
I'm
sort
of
I
got
stuck
with
it
and
I
just
basically
posted
uh
in
josh's
issue
saying
that
ah
josh
is
too
complicated.
C
I
wish
there
was
just
like
a
sort
of
like
trimmed
down
version
of
josh
and
and
jeff's.
Like
oh,
have
you
seen
b
like
this,
we
wrote
that
for
that
exact
purpose,
I'm
like
oh
well,
sorry,
I
went
and
checked
that
out
and-
um
and
that
was
perfect-
it
was
like
the
code
was
much
simpler.
It
was
written
for
backdrop
from
scratch,
sort
of
thing
and
it
also
didn't
have
multi-site
support,
but
I
was
able
to
do
that
and
make
a
pull
request
and
get
that
working
much
more
easily.
C
um
So
with
sort
of
my
work
in
there
and
then
jeff
uh
made
me
as
a
maintainer
there
and
yeah.
That's
how
I
started
working
with
b,
and
I
see
it
as
basically
being
josh
for
backdrop
but
ringing
from
scratch.
Without
all
the
overhead
of
like
composer
or
the
previous
code,
pile
like
alan
was
saying
all
the
extra
code.
That's
unneeded
lots
of
stuff.
um
So
lately
um
for
the
past,
12
months
or
so,
I've
been
the
primary
maintainer
of
b
and
I've
been
basically
refactoring.
C
The
entire
code
base,
partly
to
fix
a
an
issue
with
it.
Where
I
think
different
commands.
Could
you
have
like
the
same
command,
be
running
two
different
bits
of
code?
It
was
a
bit
confusing,
and
so
there
was
an
issue
about
how
to
fix
that
up.
So
as
part
of
fixing
that
up,
I
then
just
took
the
opportunity
to
go
through
the
whole
code
base
and
just
clean
up
a
bit
fix
it
up,
make
it
more
stable,
more
standardized
that
sort
of
thing
and
so
on
and
off
the
last
12
months.
C
I've
been
doing
that
and
I've
finished
pretty
much.
All
of
that.
There
is
just
one
issue
left
which
is
just
getting
the
test:
php
unit
tests
working
um
and
then
I
think,
I'm
going
to
be
ready
to
launch
version,
one
of
the
which
will
be
the
sort
of
stable
version.
We
can
then
build
off
for
the
future,
um
so
yeah.
C
My
plan
has
been
not
to
sort
of
add
new
functionality
yet
sort
of
thing,
but
just
get
the
b
to
be
more
stable
and
ready
and
then
once
version
one
launches
which
hopefully
in
the
next
month
or
so
then
um
then
we
can
then
start
adding
new
features.
New
commands,
sort
of
build
it
up
to
be
sort
of
more
similar
to
where
brush
and
trush
is
in
terms
of
feature-wise.
E
C
Repository
um
so
yeah,
one
of
the
things
I
want
to
point
out
with
with
b,
is
that
it
is
under
active
development
and,
as
such,
there
might
be
breaking
changes.
So
unlike
backdrop
core,
where
we
try
to
be
backwards,
compatible
and
not
break
things
with
the
before
I
came
onto
the
project
and
also
since
I've
been
on
there,
it's
been
the
thing:
that's
like
we're
actively
building
it,
maintaining
it
and
we're
just
going
to
be
probably
breaking
things
fixing
and
that
sort
of
thing,
so
I've
kept
that
disclaimer
there.
C
um
Just
so
people
know
that
if
you
find
a
bug,
it's
like
something's
not
working
the
way
it
should
be.
You
need
to
change
something
we
will
change
it,
we'll
fix
it.
It
might
break
things
but
we'll
put
out
once
we
do
a
stable
version
release
we'll
put
out
um
like
release,
notes
for
each
version
to
say,
what's
been
changed
and
whatever,
um
but
one
other
thing,
I'm
not
not
sure
where
brush
and
rush
are,
but
I'm
not
familiar
with
microsoft
windows
much
in
terms
of
especially
console
things,
but
apparently
doesn't
work
with
windows.
C
um
That
was
the
case
from
that
first
style.
I
believe
so,
I'm
not
sure
if
that's
one
of
the
differences
between
people
wanting
to
evaluate
one
versus
another
tool
but
yeah.
If
the
apparently
doesn't
work
with
windows
unless
there's
people
that
want
it
to
work,
then
I'm
not
going
to
pull
requests
on
that.
I'm
not
familiar
with
that,
um
but
yeah
there's
instructions
here
on
how
to
get
it
working
on
your
system
um
and
I've
got
my
set
up
here
now,
I'm
using
lando.
C
So
it
seems
to
be
a
little
bit
different
from
maybe
if
you've
just
installed
b
on
your
server
or
your
computer
um
directly.
um
But
this
is
actually,
as
part
of
my
writing
and
fixing
the
tests
for
b.
um
I've
got
a
lando
file
chips
with
b
and
that's
like
development
purposes,
and
also
I'm
hoping
that
we'll
be
able
to
use
this
for
running
tests
against
any
poor
person
future.
So
this
lambo
file.
C
Does
different
things
and
one
of
them
is
that
it
sets
up
three
backdrop
sites.
So
one
backdrop
site
is
just
a
backdrop
instance
like
a
backdrop
folder,
and
it's
just
using
a
normal
backdrop
as
you
would
probably
most
people
would
use
it
and
then
it
installs
a
separate
backdrop
instance
called
multi-site
and
instead
of
using
the
normal
way
of
installing
it,
it
uses
the
multi-site
setup.
C
A
C
um
Yeah,
so
if
you're
wanting
to
run
commands
uh
against
your
backdrop
site
and
that's
what
these
tools
are
for
and
they'll,
let
you
do
something
like
um
like
this
and
you
can
get
information
about
a
backdrop
site
so,
as
I
said
for
me,
lando
I'm
using
lambo
so
because
that
I
have
to
preface
everything
with
lando.
But
if
you're
running
being
yourself
on
your
own
server,
then
you
just
write
the
status
now
in
this
case,
I'm
running
it
outside
of
a
backdrop
directory
and
I
haven't
specified
which
backdrop
directory
I
want
to
use.
C
C
B
C
So
now
I'm
into
one
of
my
multi-site
specific
sites.
If
I
run
the
same
command
now
I
see
that
it's
a
multi-site,
the
site
directory
is
multi-one,
which
is
where
we
are
and
gives
information
about
this
particular
site
so
b.
Can
I
mean
status
is
just
one
of
the
commands
that
that
you
can
use
to
give
you
information
about
your
backdrop,
installation
um
but
yeah.
What
I
was
trying
to
show
you
is
the
um
ability
for
me
to
better
use
multi-sites,
as
well
as
normal
backup
installations.
C
So
normally
you
just
write
b
and
then
any
global
options,
the
command
you
want
to
use
and
then
any
command
specific
options
or
arguments.
After
that,
the
global
options
are
these
four
so
root?
Lets
you
specify
which
backdrop
installation
you're
wanting
to
target
with
whatever
command
you're
running,
so
you
can
either
run
the
command
from
within
the
backup
installation
or
if
you
can't
do
that,
for
whatever
reason
you
can
specify
the
global
option
and
that'll
tell
it
which,
which
installation
you're
targeting
and
the
same
with
site.
C
So
if
you
are
using
multi-site
um
as
well
as
telling
it
which
pack
of
insulation
to
use
you
can
tell
every
site
like
specific
site,
you
want
to
type
it.
So
if
you're
wanting
to
run
chrome
or
communications
or
whatever,
you
want
to
tell
exactly
which
site
you're
trying
to
do
that
for,
and
you
can
do
that
with
that
option.
C
C
C
C
C
C
Every
other
issue
in
here
is
just
an
enhancement
that
is
just
going
to
add
more
functionality
or
make
things
better,
and
that's
why
um
we
will
be
adding
more
commands
and
then
and
more
functionality
um
once
we
launch
version
one
so
we're
trying
to
focus
on
just
getting
that
done
at
the
moment.
So,
while
there's
not
many.
C
That
people
are
used
to
maybe
josh.
For
example,
we
do
have
some
some
basic
ones
in
there
like
clearing
cage
for
a
site
um
getting
and
setting
config.
Since
that's
what
backdrop
uses,
instead
of
like
drupal
variables,
running
chrome,
um
disabling
projects,
enabling
projects
downloading
projects
or
backdrop
for
yourself
um
installing
a
site,
so
you
can
sort
of
have
a
backdrop,
installation
ready
to
go
and
then
you've
actually
installed
the
sitemap.
C
You
can
get
the
database
connection
information
and
install
the
site
using
b,
um
show
any
sort
of
watchdog
log
messages,
get
information
about
the
projects
on
your
site,
modules,
things
or
layouts
status.
What
I
showed
you
for
some
theme
and
they
like
setting
admin
or
default
theme
to
commands
there
for
that,
and
I'm
doing
database
updates
and
uninstalling
stuff.
So
obviously
some
of
the
ones
we
want
to
get
added,
which
has
been
quite
popular,
have
been,
like
tim
said,
um
making
it
so
that
you
can
automatically
log
into
a
site
or
reset
the
password.
C
C
C
So
if
I
run
that,
so
it
develops
downloaded
into
the
core
modules
directory
in
the
multi-type
installation,
and
we
can
see
that
here.
So
in
the
normal
backdrop,
there's
no
devel
there,
because
that
one
wasn't
targeted,
uh
multi-site
was
targeted
and
that's
where
it
put
development.
So
now
we
log
in.
C
So
that
that's
downloaded
to
go
into
the
core
directory,
so
all
my
multi
sites
can
access
it.
Now.
If
we
wanted
to
target
um
one
of
them,
then
I
mean
it
doesn't
matter
where
you
put
the
global
commands
before
at
the
end.
So
I'm
and
one
of
the
things
I
did
when
I
was
adding
the
multistar
functionality
is
I
made
it
so
that
you
can
specify
site
and
then
in
the
sites.php
file
you
have
the
url
of
the
site
and
then
you've
got
the
directory
name
um
within
the
site.
C
C
C
Myself,
well,
that's
definitely
something
that
can
be
fixed
and
I
think
that's
something
that
I've
come
across
before
because
that's
all
that's
annoying.
So
if
we
want
to
fix
that
all
right,
so
now
we
want
the
modules
to
simplify
but
not
multitude
that
wasn't
affected.
So
this
is
how
you
can
use
b
to
install
uh
projects
and
run
commands
on
specific
websites,
even
within
the
multi-site
installation.
C
C
C
um
I
haven't
come
across
that
myself,
but
obviously
there's
if
there's
a
need
for
that,
we
can
open
an
issue
and
getting
that
editing
I
mean
for
my
from
my
point
of
view.
I've
used
certain
commands
from
drush
a
lot
and
others
not
at
all,
so
there's,
obviously
a
range
of
stuff
out
there
that
that
people
might
want
that
I've
never
come
across.
So
certainly,
um
if
you're
looking
at
some
of
that,
then
you
have
an
issue
and
um
and
getting
that
editing.
B
I
I
just
want
to
add
to
robert's
questions
that
that
one
of
the
main
reasons
why
we
started
to
use
using
brush
without
you
know
uh
disturbing
the
other
two
projects,
because
we
knew
that
it
would
take
some
time
to
implement
this
database
comments.
But
I
would
like
to
say
that,
as
soon
be
project
starts
supporting
database
commands,
we
are
more
than
happy
to
switch
to
b
and
start
even
contributing,
uh
unfortunately,
to
many
other
things
that
we
do
not
have
time
to
work
on
on
b2,
because
brush
has
all
the
database
features.
B
B
C
No,
so
I
think
I've
I've
just
looked
in
the
issue
queue
and
there
is
an
issue
I've
created
for
um
adding
commands
to
import
and
export
databases.
So
that's
obviously
something
yet
to
come.
um
When
we
do
add,
commands
is
one
of
the
part
of
the
refactoring
I've
been
doing
over
the
last
12
months
is
being
to
try
to
get
away
from
the
sort
of
drupal,
specific
wording
or
stuff
that
was
used.
C
um
So,
for
example,
with
the
I
can't
think
of
something
on
the
top
of
my
head,
but
I
know
with
like
the
status
command
um
there's
an
alias
st
which
works.
I've
also
made
an
alias
info
just
because
that
seems
to
make
sense
as
well,
um
so
where
I've
got
command
names,
I've
somehow
sometimes
changed
them
to
the
other,
just
a
bit
more
simpler
or
something
that
makes
a
bit
more
sense.
I've
kept
as
much
as
I
can.
C
The
aliases
for
people
that
were
using
drush
together
come
in
and
do
the
same
sort
of
thing,
but
this
is
part
of
where
the
breaking
changes
may
occur.
There
might
be
differences
in
how
things
work,
but
as
much
as
possible,
we'll
try
to
keep
aliases
at
least
working,
so
that
the
same
command
words
can
be
used
between
the
different
ones,
um
but
yeah
there's
definitely
an
issue
for
opening
adding
database
import
and
export
commands.
At
least
thank
you.
A
C
um
Yeah,
I
think
just
getting
an
idea
of
what
people
want
from
from
this
like.
As
I
said,
I've
used
some
commands
a
lot,
none
others
not
at
all,
so
getting
an
idea
of
what
people
wanting
opening
issues
say:
hey.
I
really
love
this
command
from
josh,
or
I
really
like
this
functionality
that
even
josh
didn't
do
or
what
I
don't
know.
Maybe
trust
us
everything.
um
So
yeah
posting
the
issues.
What
you're
wanting
to
see
if
you're
a
developer-
and
you
think
you
can
help
out
with
with
writing
the
code
to
implement
those
issues.
C
You
can
certainly
go
ahead
and
start
doing
that
um
I've
got
there's
only
two
branches
in
b.
One
is
the
main
one.
The
other
one
is
the
one
I'm
currently
doing
the
test
stuff
in
it
has
a
slightly
updated
like
lambo
file,
which
I've
accidentally
put
into
that
branch
instead
of
the
other
one.
But
apart
from
that,
the
main
branches
is
sort
of
ready
to
go
in
terms
of
the
commands
are
all
like
sort
of
standardized.
C
The
way
that
they're
written
there's
an
api
um
markdown
file,
which
explains
um
how
the
api
side
of
things
works.
So
if
you
want
to
use
that
to
start
writing
their
own
commands,
you
can
certainly
go
ahead
and
start
doing
that,
um
and
I
mean
I'm
currently
working
through
the
test
getting
that
working.
I
should
be
done
within
like
a
week
or
two
a
few
weeks
uh
max
um
and
then
hopefully
push
that
in
merge,
it
all
and
then
release,
hopefully
more
stable
version
one,
and
then
we
can
focus
on
starting
to
more
functionality.
C
A
C
So
it
depends
on
the
command.
I
mean
in
terms
of
just
adding
the
code
to
b.
It's
very
simple:
you
just
can
look
at
the
the
api
documentation
that
I've
written
and
copy
that
or
any
other
command
just
copy
that
there's
basically
one
function
that
defines
your
command.
It
tells
it
what
the
name
of
the
command
is,
what
the
aliases
are.
um
What,
if
any
bootstrap
level
backdrop
needs
to
be
at
in
order
to
run
the
command
some
commands
like
um
downloading
a
project,
you
don't
need
backdrop
to
be
sort
of
up
and
running.
C
B
Add
on
this:
if
people
start
pull
requests
and
they
want
to
implement
some
kind
of
command
they
need,
but
they
have
no
idea.
They
can
look
for
the
similar
command
on
brush
because
the
syntaxes
are
pretty
similar
and
you
know
uh
just
not
to
copy
whatever
you
know
brush
carries.
As
I
said,
it
has
lots
of
dirty
code,
but
basically
they
can
have
an
idea
at
least
from
brush,
because
it
is
in
most
of
ways
seen
the
implementation
of
commands
similar.
I
I
I
did
compare
thanks.
Okay,.
C
C
If
I'm
implementing
commands
or
other
people
want
to
write
broadcast,
then
yeah
I'll
likely
be
checking
out
how
josh
or
brush
did
it
um
because
it
to
answer
tim's
question
it
really
does
depend
on
the
command
like
if
you're
wanting
to,
for
example,
write
a
command
that
synchronizes
a
website
of
one
server
with
the
website
for
another.
That's
probably
going
to
be
a
lot
more
involved
than
just
running
chrome.
On
a
website
I
mean
literally,
the
the
command
to
run.
Kron
is
just
the
backdrop
function
for
running
from.
C
That's
it
basically,
so
it
depends
on
the
command
as
to
how
complex
it
is,
um
but
the
simpler
ones,
I
think,
would
be
quite
easy
for
people
to
do,
even
if
they
have
just
a
little
bit
of
experience
with
requests
or
writing
code.
um
It
shouldn't
be
too
hard
to
copy
what's
there
and
then
just
tweak
it
a
bit
for
what
you
need.
um
Obviously,
the
more
complex
stuff,
and
I'm
myself
probably
gonna,
need
help
too,
with
especially
the
database
stuff,
maybe
so
yeah.
A
C
Maybe
I
mean
weeks,
I
don't
know
I
mean
I've
been
doing
in
my
spare
time
just
on
enough,
I'm
trying
to
focus
on
that
as
opposed
to
other
things
just
to
try
and
get
it
done,
because
I
said
it's
been
like
12
months
on
and
off.
I
was
doing
it
for
a
few
months
solid
and
then
I
got
distracted
onto
all
this
stuff
and
I
forgot
about
it
and
I
come
back
two
months
later,
but
now
I'm
really
just
trying
to
push
and
get
it
done,
because
I
know
that
people
are
waiting
on
it.
C
D
Martin,
you
had
a
question
uh
yeah
when,
when
you
were
showing
the
uh
the
the
git
directory
you
had
composer
in
there.
I
think
one
of
the
problems
with
drupal
polite
was
you
uh
particularly
for
a
lot
of
people
who
were
maybe
a
bit
more
amateur
developers
like
me
um
is:
is
that
drush
worked
absolutely
fine
on
shared
hosting
but
composer
didn't
uh
at
all,
so
it
is
be
dependent
on
composer
because
it
it
send
with
um
drupal
8.
D
C
So,
with
composer
yeah
you,
um
you
would
have
seen
that
on
the
repository
on
github,
that's
that's
showing
the
one
dot
x
branch
um
on
my
latest
branch.
I've
been
doing
the
main
work
with
running
the
tests
and
stuff
part
of
my
fixing
up.
The
test
was
removing
composer,
because
all
the
composer
was
doing
was
just
installing
php
unit
and
I
think
something
else,
other
drupal
coding
standards
to
sort
of
test
against
that.
But
I've
now
just
got
that
directly
in
the
lando
file.
So
I
actually
remove
composer
in
the
latest
version.
C
So
there
is
no
composer
for
v
now,
so
you
won't
need
that
and
that's
part
of
the
reason
I
like
b
over
other
projects
and
and
as
alan
was
saying
why
they
fought
brush
brush
previous
to
all
the
composer
stuff,
because
it's
just
it's
unnecessary
for
something
like
backdrop,
so
yeah
so
b
doesn't
need
composer.
That's
been
removed
in
the
latest
version
which
I'll
merge
in
soon
and
as
for
other
platforms,
I've.
I
personally
have
a
virtual
private
server
that
I
have
on
my
websites
on
I've
installed
beyond
there
and
it
works
fine.
C
A
C
Yeah,
um
I
think
I
have
worked
with
those
with
drush,
but
mainly
on
drupal
7
or
drupal
8
sites.
I
haven't
actually
done
anything
with
that
in
backdrop,
so
not
sure
how
that
would
work
with
backdrop,
um
but
again,
just
if
it's
something
that
you're
wanting
you
can
open
an
issue
and
if
you've
got
the
knowledge
to
do
it
by
all
means.
C
If
not,
then
I
can
try
and
look
at
how
josh
or,
if
brush,
does
that
too
and
try
and
copy
that
in
in
future,
but
um
but
yeah
we
are
wanting
to
make
it
as
feature
complete
as
possible,
so
that
um
I
mean
jeff
said
that
he
sort
of
sees
b
is
the
future
for
backdrop.
So
if
we
can
get
it
as
feature
complete
as
possible,
then
we
might
need
all
these
different
commands.
We
just
focus
on
one.
A
G
D
A
For
those
that
don't
know
jeff,
do
you
you
still
work
with
lando
or
onlando.
Are
you
still
involved
in
the
project?
Yes,
yes,
okay,
so
jeff
actually
doesn't
just
work
with
lando
but
works
on
lando.
So
um
one
of
the
first
things
I
ran
into
in
saying:
okay,
I'm
gonna
try
out
b.
So
I
installed
it
locally
um
was
able
to
like
download
modules
and
stuff
and
then
realized
that
I'm
using
lando.
C
Well,
it's
in
the
forum
for
now
I've
got
an
issue
open
to
add
it
to
the
repository,
I'm
just
not
sure
where
the
best
place
is
for
that,
whether
I
should
just
put
a
in
the
um
readme
file
or
whether
I
should
start
using
the
the
wiki
for
stuff
like
that.
um
So
I've
got
an
issue
there
for
that
which
I'll
I'll
look
at
that,
but
it
does
have
a
link
to
the
the
forum.
If
anyone's
wanting
that
information
now,
then
that's
available
on
the
forums.
A
A
No,
he
is,
um
uh
I
think,
that
um
there's
a
bias
away
from
sort
of
stressing
things
like
command
line
tools.
In
the
backdrop
community
because
of
um
a
lot
of
people
have
come
to
backdrop
because
of
like
being
afraid
of
or
or
not
liking,
the
complexity
of
tools
like
composer,
and
there
are
still
a
lot
of
drupal
developers
that
don't
use
brush,
um
and
I,
I
think,
there's
a
little
bit
of
a
fear
that
we
don't
want
to
make
uh
uh
scare
people
away
that
aren't
used
to
these
tools.
A
A
So
I'm
really
glad
to
see
some
progress
here,
because
I
think
you
know,
uh
I
think,
there's
really
a
need
and
space
for
it
in
the
background,
so
I'm
not
a
heavy
drush
user
or
or
be
user,
but
I
do
rely
on
it.
You
know
regularly,
so
it's
nice
and
I'm
excited
to
get
to
cb
get
there.
So
I
can
settle
on
just
one
tool.
C
E
Great
question
in
drush
there's
the
ability
for
module
developers
include
their
own
drush
commands
um
and
the
example
I'm
thinking
of
is
in
civi
crm,
which
has
its
own
database
update,
drush
command.
You
run
cb
upd,
to
update
a
service
here
on
and
and
does
b
have
that
that
same
ability
um
so
that,
for
example,
the
backdrop
port
of
city
crm
would
include
uh
the
b
command
to
do
a
database
update.
C
Yep,
um
I
believe
that
something
that
jeff
or
one
of
the
previous
um
sort
of
contributors
added,
uh
which
is
still
in
there
I
haven't
like
sort
of
tested.
It
fully,
um
obviously
just
been
focusing
on
the
core
commands,
but
I
believe
there
is
the
code
in
there
that
looks
for
um
certain
file
names
in
certain
places
to
pull
in
other
commands
um
so
definitely
worth
investigating
that,
but
that
should
be
there
and
working.
I
believe.
A
A
Else
pretty
sure
that
probably
most
of
the
people
on
this
call
from
my
personal
knowledge
use
or
from
their
comments
already
do
use
uh
brush.
So
if
anybody
was
looking
for
like
a
more
of
an
introduction
than
you
got
today,
let
us
know-
and
maybe
we
can
point
you
at
some
resources,
but
fundamentally
I
think
uh
bro
b
seems
to
work
a
lot
like
um
trash.
So
here's
a
question
I
have
as
preparing
for
this
virtual
user
group
and
having
to
post,
tweets
and
and
uh
event
notifications
on
the
topic.
A
Can
we
say
anything
more
about
how
we
want
to
talk
about
it
or
brand
it,
because
every
time
I
like
to
write
the
letter
b,
it's
like
do,
I
put
it
in
quotes.
So
people
understand
that
I
didn't
just
forget
to
finish
my
word.
uh
You
know
what
do
I
do?
It
just
feels
really
uh
kind
of
weird.
How
will
I
get
used
to
that.
A
C
Yeah,
what
do
you
think
of
people
right
backdrop
console
and
then
brackets
b
and
quotes
um
when
I'm
referring
to
it
in,
like
in,
like
a
public
group
that
people
might
not
understand,
if
I'm
just
talking
to
someone
who
already
knows
what
I'm
talking
about
to
say,
b,
to
make
it
easier,
but
yeah
sometimes
just
expand
it
out.
If
you
sort
of
want
to
avoid
confusion,
alan.
B
Well,
this
is
crazy
suggestion,
but
we
uh
picked
up
brush
specifically
because
it
was
fancy.
It
resembled
rush
and
uh
you
know
at
the
same
time
it
was
obvious
it
is.
uh
It
is
not
brush
because
it
has
first
letter
replace
for
b.
So
since
we
are
going
to
discontinue
brush
as
b
matures,
we
can
start
using
brush
if
you
want.
A
A
A
A
It
needs
some
attention
to
make
that
work
for
people
that
don't
really
care
about
configuration,
management
and
people
that
really
care
about
configuration
management,
because
that's
that
really
can
make
a
developer's
life
difficult.
If
that's
a
process,
that's
just
hard
to
work
with
so
I'll.
Just
I'll.
Just
say
that
in
that
you
know,
as
as
as
b
becomes
the
defaults
for
the
backdrop
project.
G
There's
a
there's,
an
issue
for
it
in
the
bq,
and
one
thing
I
would
say
about
that
is
the
backdrop.
Truss
extension
has
a
backdrop
configuration
import
and
configuration
export,
so
we
could
just
take
those
and
port
them
to
b
instead
of
starting
from
scratch,
so
there
is
existing
work
that
could
be
leveraged
instead
of
starting
from
scratch.
K
A
Because,
if
you
wouldn't
make
it
b,
I
would
make
an
alias
that
would
be
b
to
run
it.
So
so
that's
already
done.
It's
totally
done.
Good
point,
good
point.
um
I
uh
so
just
just
some
quick
announcements:
um
we
did.
We
did
uh
a
virtual
user
group
two
weeks
ago.
uh
We
did
one
today,
that's
the
most
we've
done
in
a
four
week
or
a
four
week
period.
um
I've
con
there's
a
lot
of
topics
I
would
like
to
cover,
so
I'm
inclined
to
sort
of
keep
doing
them
on
a
frequent
basis.
A
I'd
love
to
hear
what
other
topics
uh
we
have
an
outstanding
request
that
we've
been
working
on
for
a
while
to
do
something
on
writing
tests.
I'd
also
like
to
do
some
more.
um
You
know
beginner
friendly
topics,
uh
however,
in
two
weeks
from
now
we'll
be
doing
in
about
two
weeks
we'll
be
doing
the
our
next
backdrop
live.
A
So
I
think
we'll
take
a
little
bit
of
break
between
the
virtual
user
groups,
uh
but
everybody
if
you're
on
this
call
you
hopefully
you
know
about
backdrop,
live
we
did
a
a
48
hour
a
two
day.
uh
It's
like
our
online
camp
uh
backdrop
camp.
We
did
one
in
september
that
went
pretty
well,
uh
we
had
about
60
people
register
for
it
and
we
had
up
to
30
or
40
people
online
at
a
time
and
we're
doing
a
short,
a
slightly
shorter
version
a
week
from
this
coming
friday.
A
Well
in
at
least
in
the
part
of
the
world
I'm
in
for
peter
it
would
be
a
week
uh
from
saturday
um
we're
these
are
uh
uh
unconference
uh
sort
of
style.
So
you
bring
us
your
topics
that
you
want
to
talk
about
we'll
schedule
sessions.
People
can
do
little.
Demos
it'll
be
somewhat
impromptu.
We're
not
asking
people
to
do
big
prepared
presentations.
A
If
you
do
want
to
do
some
kind
of
a
presentation
and
record
it
in
advance,
you
can
and
then
we
can
use
uh
backdrop
live
to
talk
about
it.
So
um
we
we
officially
just
made
the
registration
live
last
night
for
backdrop
live
um
we
were
asking
for
a
donation,
a
voluntary
donation
with
registration,
and
I
think
john
right
now
is
maybe
not
here,
because
she's
working
on
fixing
problems
with
our
paypal
account
so
that
we
can
accept
those
donations.
A
But
you
could,
in
theory,
still
register
right
now
because
it
works
without
the
donation
form,
and
then
you
can
always
come
back
and
give
us
a
donation
later
so
feel
free
to
run
over
to
the
website
and
uh
and
register.
Give
me
any
feedback
on
that
process.
We
will
be
added.
The
the
site
might
be
a
little
information,
sparse
right
now,
we'll
be
adding
that
and
as
people
register
and
tell
us
what
they
want
to
talk
about.
A
A
Okay,
any
other
announcements
that
anybody
else
has
for.
In
the
backdrop,
world,
okay,
um
so
expect
the
next
user
group
to
be
in
about
four
weeks
um
and
I'll
try
and
get
an
announcement
out
about
that
soon,
although
there
might
be
a
little
bit
of
break
after
backdrop
live
as
we
recover
from
our
24
hour,
sprint
of
backdropping.