►
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
https://wasmcloud.com
A
B
I
checked
I
I
just
like
watching
you
realize
it
live,
no
okay,
yeah!
Let
me
do
the
thing.
Okay,
so
today
is
going
to
be
a
relatively
quick
just
kind
of
talking
through
it
demo,
but
it's
it's
a
significant
improvement
that
was
really
causing
some
pain,
at
least
for
us
as
well
some
cloud
developers
for
a
little
while
so
going
back.
This
isn't
quite
on
main.
This
is
just
one
commit
before
maine,
since
we
got
it
merged
in.
B
If
you
look
at
the
wasn't
cloud
host
folder,
which
is
a
phoenix
application,
so
it
uses
both
elixir
and
phoenix
live
view
to
give
like
the
dashboard
view
and
then
underline,
there's
also
our
rust
functions
for
things
like
generating
gnats
and
keys,
and
things
like
that.
B
So
from
the
base
level,
when
you're
looking
at
this
host,
when
you
build
the
application,
you're
going
to
need
an
elixir
tool
chain
and
you're
going
to
need
a
rust
tool
chain
to
build
both
of
those
both
the
parts
of
our
project,
something
that
really
frustrated
us
for
a
while
is
with
phoenix,
I
think
it's
1.59
or
1.5.9,
whichever
one
it
used,
npm
dependency.
So
it's
not
like
because
we're
using
live
view.
We
got
to
fully
escape
javascript
and
css
things
with
web
development.
B
So
in
order
to
actually
build
the
project,
you
needed
a
node
npm
installation
to
install
like
the
static
assets.
So
you
know
as
part
of
our
our
installation
process,
you
had
to
install
the
assets
that
you
need
for
the
server
and
even
from
our
ci
cd
perspective.
This
was
taking
like
an
additional
step.
You
needed
to
install
node,
specifically
node
14.
That
was
the
one
that
worked
and
for
our
arm
builds.
You
also
needed
to
install
python.
B
This
was
due
to
I
think,
node
sas
the
some
dependency
there
needed
python
2.7
to
cross-compile
to
arm.
So
in
order
to
build
our
elixir
and
rust
application,
you
also
needed
python
and
node
and
that
really
irked
us
from
a
developer
perspective,
but
thankfully,
with
phoenix
1.6.
What
we
have
is
the
ability
to
instead
of
use,
npm
use
es
build.
So
if
we
go
to
main
under
wasm
cloud
host,
you'll
notice,
now
we've
kind
of
updated
our
prerequisites.
You
don't
need
to
excuse
me,
you
don't
need
to
install
node
anymore.
B
B
So
that
again
you
don't
have
to
install
additional
things
other
than
just
elixir
and
a
rust
tool
chain,
and
this
little
es
build
es,
build
rule
will
use
the
the
sas
compiler
to
compile
our
static,
css
and
and
javascript
files
and
then
place
them
into
a
directory
where
the
wasm
cloud
host
can
find
it.
So
again,
this
isn't
really
too
much
of
a
demo.
I
will
show
you
just
for
fun
that
little
make
yes
build
rule.
B
So
this
is
something
that
actually
ended
up,
dropping
our
container
size
by
a
megabyte
which
is
cool,
and
it
also
speeds
up
speeds
up
rci
to
release.
Wasn't
cloud
host
but,
most
importantly
now,
if
you're
looking
at
developing
wasmcloud
or
on
the
wasmcloud
host,
you
don't
have
to
install
a
bunch
of
extra
language
tool
chains
just
to
work
in
elixir
and
rest.
So
we're
pretty
excited
about
this.
This
was
on
our
like
things
that
annoy
you
every
everyday
backlog
for
a
while.
B
So
we're
pretty
happy
to
get
that
done
and
if
anybody
else
is
using
a
phoenix
application
and
is
interested
in
upgrading
from
a
pre,
1.6
or
1.60,
I
keep
forgetting
the
process
was
actually
fairly
simple,
even
though
we're
using
like
a
custom,
some
custom,
javascript
javascript
library
to
like
do
the
layout
of
our
wasn't
cloud
host,
it
wasn't
too
bad,
please
you
know
you
feel
free
to
hit
me
up
in
slack.
I
can
give
you
the
you
know:
they
wrote
a
great
migration
guide
to
go
from
npm
to
es
build
so
yeah.
B
That
is
pretty
much
all
I
had
for
the
demo
today.
Anybody
have
any
questions
about
this
or
or
like
what
the
migration
process
was
like.
B
If
not,
then
I
will
take
the
shared
excitement
to
kill
mode
out
of
our
out
of
our
back
end
project.
A
Great
work
force,
I
think,
you're
actually
up
next
for
community
call-outs.
Do
you
maybe
want
to
share
any
community
call-outs
you
have
for
today.
B
Sure
so
I'll
go
ahead
and
hand
off
to
brooks
hey
guys,
I'm
doing
the
community
call-outs.
So
I
gotta
keep
it
interesting.
So
I
have
three
three
community
call-outs
this
week,
they're
all
focused
around
the
host
and
now
that
you
don't
even
need
to
install
node
or
python
or
anything
to
get
this
working.
It
should
be
easier
than
ever
to
contribute
to
the
the
wasn't
cloud
otp
host,
and
I
know
that
some
people
were
asking
in
the
in
the
community
slack
this
morning
on
good
places
to
start
contributing.
B
B
So
the
first
one
here
is
around
link
definitions.
When
you
try
and
overwrite
an
existing
link,
definition
providers
are
specifically
coded
in
wasmbus
rpc.
You
don't
actually
have
to
do
this
directly
in
your
provider
code,
they're
coded
to
ignore
duplicate,
link
definitions-
and
this
is
for
this
is
so
that
link
definitions
can
be
item,
potent
and,
and
we
can
establish
them
without
or
we
can
re-establish
them
without
worrying
about
overriding
old
link
definitions,
but
it
turns
out
in
the
host
for
a
specific
scenario
described
in
this
issue.
B
We
can
actually
ignore
a
duplicate
link,
definition
on
the
provider
side,
but
then
overwrite
it
in
the
host
cache.
So
this
is
something
that
can
cause
confusion
and
is
really
an
easy
scenario
to
to
catch.
If
a
link
definition
exists,
don't
overwrite
it
in
the
local
cache.
So
this
would
be
a
great
place
to
great
place.
To
start
the
next
one
is
semi-related
to
a
bug
that
we
found
in
quash.
B
It's
that
the
dashboard,
when
you're
establishing
a
link
definition,
it
can't
handle
base64,
config
base64,
encoded
values
like
you
can
see
here
generally
end
with
like
a
double
equal
sign,
or
I
mean
at
least
it
happens
sometimes,
and
the
way
that
we
do
the
values
splitting
in
the
washboard
is
by
splitting
on
an
equal
sign.
So
when
you
do
this,
you
end
up
getting
config
base64
this
value
and
then
two
empty
values.
So
really
the
what
we
need
here.
B
B
This
would
be
something
that
anyone
who's
dealt
with
parsing,
base64
or
touch
stuff
like
this
will
be
able
to
take
a
poke
at
it's
a
small
little
contained
section
of
code,
so
great
place
to
start,
and
then
the
last
one
is
when
we
write
the
when
we
write
the
host
config,
which
is
every
time
we
launch
the
host
with
new
parameters,
whether
it's
from
environment
variables
or
explicitly
providing
things
in
the
host
config,
we
write
out
to
a
json
file.
B
So
when
you
launch
a
new
host,
it
automatically
connects
to
the
lattice
that
you
configured
last.
This
is
actually
a
really
simple
rename
that
would
have
a
big
impact.
We
write
that
value
out
to
rpc
underscore
timeout
and
we
should
be
writing
it
out
to
rpc
underscore
timeout
underscore,
ms,
so
just
a
little
naming
issue
again.
These
are
things
that
are
like
really
quick,
great
way
to
contribute
your
first
thing
and
will
certainly
take
this.
B
Would
this
would
certainly
help
with
defining
an
rpc
timeout
across
multiple
hosts
in
the
same
lattice,
so
that
is
the
community
call
out
it's
all
about
the
host
and
getting
some
small
elixir
things
in
today.
As
usual,
I
will
put
these
in
the
community
slack
for
people
to
pick
up
and
then
we'll
tweet
them
out
a
little
bit
after
this
meeting.
B
Yeah
just
just
to
wrap
this
up.
If
anybody
has
any
questions
about
these
community
call-outs
or
about
these
issues
right
now,
if
you're
interested,
I
can
answer
any
questions.
If
you
want
to
take
a
stab
at,
it,
feel
free
to
just
leave
a
comment
on
the
issue
and
say
that
you're
interested
in
taking
a
look
at
it.
A
That's
great
brooks
thank
you
so
much.
You
know
open
floor
for
any
sort
of
call
outs
from
the
community
today
or
any
discussion
topics.
Questions
proposals,
anything
along
those
lines.
A
Okay,
I
think
we
may
wrap
this
one
up
a
little
early
today,
folks,
as
usual
I'll
go
and
stop
recording
and
we
can
oh
stuart
go
ahead.
C
Sorry
before
before,
you
did
just
just
a
quick
call
out
so
two
weeks
today
we're
doing
another
event
red
badger,
which
is
we
love
nats.
I
don't.
If
you
remember
two
weeks
two
months
ago,
probably
brooks
and
taylor
kindly
spoke
at
an
event
about
we
love
webassembly
and
we
wanted
to
do
a
special
one
about
nats
because
there's
obviously
a
really
important
underlying
foundational
technology,
both
in
wells
and
cloud,
and
you
know
generally
for
like
distributed
applications.
So
we've
got
some.
C
We've
got
actually
derrick
collison
the
founder
of
synodia
flying
over
to
speak
in
person
and
in
the
room
which
is
great
and
we've
also
got
speakers
from
form
three
and
fleet
corps
I'll,
stick
a
link
in
the
chat.
If
anybody
wants
to
it's
a
hybrid
event,
so
same
as
last
time
virtually
attend
virtually.
So
if
anybody
wants
to
jump
in
from
this
meeting
into
that
one
afterwards
more
than
welcome-
and
yes
actually
I'd
love
for
you
to
come
over.
But
this
will
happen.
C
I
promise
you
and
I'll
put
a
link
in
the
wasn't
cloud
slack
as
well,
so
feel.
Free
to
join
us
should
be
good.
A
Thanks,
wonderful,
stuart,
thank
you!
So
much
and
we've
got
the
link
here
I'll,
go
and
make
sure
that
we
get
this
sent
out
on
our
on
our
twitter
today
and
all
of
our
socials
and
all
these
things
as
well.
Anything
we
can
do
to
help.
You
know
we
love
love
the
community
and
you
put
on
a
lot
of
a
lot
of
great
stuff
and
you're
a
huge
proponent
of
watson
cloud,
so
anything
we
can
do
to
help
is
always
always
helpful,
any
other
call-outs
or
any
other
topics.