►
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.
B
All
right,
hello,
I'm
gonna.
Hopefully
this
will
work.
Okay,
can
everybody
see
my
my
big
old
terminal
here
awesome?
So
the
first
thing
that
I
wanted
to
I
wanted
to
show
off
a
couple
of
of
upgrades
and
features
that
we've
added
into
the
the
washboard,
the
wasm
cloud
dashboard
over
the
past
couple
of
weeks.
That
haven't
quite
been
enough
to
only
show
in
a
demo
and
then
kind
of
extend
kevin's
demo
from
from
last
week
with
the
whole
jet
stream
upgrades.
B
We
now
make
use
of
jet
stream
for
our
distributed
cache
and
in
order
to
enable
that
you
just
need
the
dash
js
parameter
and
that
will
automatically
enable
jet
stream
for
gnats.
That's
all
that
you
need
to
do
and,
and
it's
functionally
the
same
as
starting-
that's
as
before,
you
just
need
a
little
parameter
so
other
than
that
I'm
gonna
go
ahead
and
get
started
by
starting
up
my
my
wasmcloud
host.
B
B
B
The
first
thing
that
I
wanted
to
show
off
is
we
have
some
additional
mechanisms
for
for
validating
user
input
and
catching
errors
before
you
put
your
runtime
in
an
unusable
state
or
or
at
least
you
get
to
a
point
where
you're
causing
errors-
and
you
don't
know
about
it.
So,
for
example,
here
I
have
the
form
fill
for
starting
an
actor
from
an
oci
registry
set
up
to
require
these
fields.
B
You
can't
do
things
like
start
less
than
one
replica
and
when
you
start
an
actor
such
as,
like
echo
2.1,
you
know
everything
everything
goes
off
without
a
hitch,
because
that's
a
oci
reference
that
we
know
about.
But
if
you
were
to
do
echo
3.4.0
or
something
that's
something
that
we
haven't
published,
we'll
go
ahead
and
give
you
in
some
little
context
here
that
we
can't
we
couldn't
find
that
manifest
for
this
resource.
B
So
you
know
you're
free
to
adjust
that
back
to
the
other
instance
of
the
actor
that
you
wanted
to
do.
You
can
actually
see
my
tests
for
aaa
that
I
was
making
sure
that
that
didn't
work
and
and
the
same
thing
will
happen
for
a
provider
from
an
oci
registry
if
you
type
in
an
oci
reference,
that's
invalid,
for
example.
B
B
Secondly-
and
I
don't
think
I
actually
have
a
provider
archive
built
locally
to
do
this,
but
all
right
well,
you
can
see
my
screen,
so
you
can
actually
see
like
the
file
thing
here.
We
actually
don't
support
you,
starting
a
a
provider
anymore
from
an
executable
which
was
very
obviously
a
big
security
hole.
B
B
Now,
if
you
look
at
my
terminal,
I
started
this
from
a
local
repository
and
and
that's
using
all
the
elixir
tooling
it's
great
for
a
development
environment
but
kind
of
a
call
to
action
and
something
that
you
all
can
do
now.
As
long
as
you
have
gnats
downloaded
is
I've
created
a
github
action
to
manually
build
the
release
tarballs,
which
is
essentially
what
we
plan
to
do
with
the
our
github
releases
anytime.
We
make
a
release
we'll
attach
the
tar
balls
for
your
architecture
and
for
your
operating
system.
B
So
for
now
we
have
linux
and
mac
os,
but
this
just
builds
it
manually.
We
can
use
this
for
development
just
for
ensuring
that
we
can
build
usable
release
artifacts,
but
I'll
I'll
go
ahead
and
link
this.
This
run
in
the
zoom
chat
so
that
you
all
can
see
it
and
I'll
send
it
out
in
the
slack
later,
but
I'm
gonna
start
another
wasm
cloud
host
with
from
from
this
archive,
just
to
show
you
what
you
would
have
to
do.
B
You
know
what
I'll
keep
it
going
for
now,
so
I've
downloaded
the
wasm
cloud
host
from
github.
This
is
actually
a
zip
file,
which
is
not
what
we
would
distribute.
It
would
be
this
this
gzip
tarball,
but
the
github
action
just
puts
it
in
a
zip
file
I'll
make
a
make
a
file
for
it
to
go
to
and
then
extract
it
to
that
folder.
B
Now,
taking
a
look
in
this
watson
cloud
host
directory,
this
is
what
you're
going
to
see
when
you
download
the
release
tarball
to
run
wasm
cloud
from
from
now
on
the
the
elixir
otp
host
instead
of
a
instead
of
a
single
binary.
It's
this
gzipped,
these
gzipped
tar
resources,
and
it
includes
a
couple
of
things
like
shared
libraries
for
the
operating
system.
B
Into
our
ci
here
is
your
with
the
wasmcloud
app,
which
just
means
that
when
you
run
wasm
cloud
host
on
your
local
machine,
you
don't
need
to
have
the
elixir
runtime
already
on
your
system,
so
this
can
be
done
from
a
fairly
basic
installation
of
of
linux.
You
need
simple
things,
but
but
nothing
like
the
full
elixir
one
time,
so
we
can
actually
run
that
using
the
wassum
cloud
host.
B
It's
like
a
shell
script
with
the
foreground.
I'm
sorry
with
the
foreground
argument
that
runs
it
and
sticks
it
in
the
and
attaches
your
terminal
to
it.
So
you
can
see
the
output
just
like
you're
used
to
and
if
we
go
back
to
our
browser,
this
is
running
on
port
4000.
We
can
see
our
other
wasn't
cloud
dashboard
and
now
this
is
the
one
that
is
running
from
the
tarball
distribution.
B
So
it's
it's
really
not
much
different,
but
you
can
see
that
after
a
few
seconds,
it
actually
is
able
to
pick
up
the
resources
from
any
other
hosts
that
are
running
in
the
lattice.
You
can
see
that
it
may
still
be
waiting
on
things
like
a
health
check
to
make
sure
that
everything
is
healthy,
but
we
can
immediately
start
our
actors
on
this
host,
for
example,
and-
and
you
can
see
this,
this
view
of
the
lattice
is
like
an
overall
lattice
view.
It
shows
resources
from
all
hosts
and
provided
everything
is
set
up
correctly.
B
Now,
the
this
is
great.
This
may
have
been
the
first
time
that
we
actually
demoed
showing
multiple
hosts
with
the
the
dashboard.
A
next
step
here
is
filtering
by
individual
hosts,
so
that
you
only
see
resources
for
a
specific
host
and
that's
something
that
we'll
demo
later,
but
the
only
other
thing
I
wanted
to
show
off
today
is
if
we
actually
close
down
all
of
these
hosts,
then
you'll
see
that
the
link
definition
that
we
created
ends
up
persisting
and
that's
thanks
to
jet
stream.
B
So
we
can
close
both
of
the
hosts
that
we
were
running
and
then
maybe
go
ahead
and
start
up
an
additional
host
from
the
the
release,
distribution
and
well,
I
didn't
I
didn't
actually
close
out
of
it.
So
maybe
the
effect
was
lost,
but
there
are
no
running
actors
or
providers,
but
the
link
definitions
persist.
Whether
or
not
you
have
a
running
host
on
at
any
time.
B
B
A
I'll
ask
some
questions
here.
You
know
now
that
jetstream's
been
you
know,
integrated
in
and
we've
got
this
great
use
case
here.
What
are
some
other
potential
use
cases?
Is
this
something
that
people
in
the
community
can
pick
up
and
use
for
their
own
applications,
or
you
know
in
their
own
apps
and
and
brooks
this
may
be
as
much
a
question
for
kevin
as
it
is
for
you.
B
C
B
The
first
initial
thing
that
comes
to
my
mind,
which
is
just
you
know
that
we're
we're
populating
more
from
jet
stream
than
just
link
definitions.
For
example
like
we,
we
populate
claims
an
oci
references,
so
we're
getting
a
nice
robust
use
of
this
cache
across
wasmcloud
as
far
as
plugging
into
your
own,
your
own
applications
wash
and
the
control
interface
supports
querying
things
from
the
distributed
cache
and
jet
stream.
B
Now
that's
a
little
nuanced,
because
a
wasmcloud
host
has
to
answer
that
query,
but
but
things
like
a
feature
that
we
haven't
supported
before
from
wash,
which
is
querying,
link
definitions
and
and
having
a
way
to
to
know
that
a
link
definition
has
been
established
is
now
possible
via
jet
stream
kevin.
I
don't
know
if
you
want
to
extend
that
answer
a
little
bit
with,
maybe
or
or
steve
with
how
community
members.
B
D
Think
one
of
liam's,
part
of
liam's
question
might
have
been
that
jetstream.
Is
this
really
amazing
distributed
cache,
distributed
key
value
store
and
we
we
might
be
able
to
introduce
a
key
either
a
back
end
of
the
key
value
capability
provider
that
could
let
somebody
use
that
distributed
cash,
distributed
fault,
tolerant
cash
with
the
key
value
provider
or
or
something
similar,
and
it's,
I
think,
it'd
be
fantastic
functionality
to
have
in
the
future.
C
A
Thank
you
kevin.
I
think
that's
more
along
the
lines
of
what
I
was
really
trying
to
tease
a
little
bit.
Is
that
worth
calling
out
on
our
backlog,
because
I
feel,
like
you
know
now
that
we
have,
you
know
validated
the
functionality
it
feels
like
that
could
be.
You
know
super
useful
from
just
a
capability
perspective.
A
All
right,
that's
great,
well,
brooks
thank
you
so
much
for
the
demo,
a
quick
community
announcements,
final
selections
for
wasm
day
for
kubecon
n
a
are
being
made
this
week.
A
round
of
questions
was
sent
out
on
a
number
of
the
submissions.
So
please
we're
going
to
try
to
get
results
announced
on
monday
of
next
week.
So
just
watch
out
for
those
I
was
really
excited.
A
A
So
if
you
can
make
it,
let
me
know
and
we'll
certainly
be
happy
to
connect
with
you
on
site
while
we're
there,
and
I
think,
that's
about
it
for
community
stuff,
a
wasm
time
meeting
is
still
out
and
running
there
and,
let's
see
update
on
the
wasn't
cloud.
Donation
should
be
finally
complete
as
of
friday
of
this
week
to
the
cncf,
so
we're
already
mostly
there
there's
still
a
couple
eyes
to
be
dotted
and
teased
to
be
crossed,
but
good
progress
along
the
board
there
and
then
I
think
steve.
A
D
You
bet
so
we
closed
43
issues.
Last
week,
I'm
doing
weekly
updates
in
the
general
channel
on
weslen
cloud
slack.
So
please
please
follow
on
there.
We
have
some
new
repos
there's
a
interfaces,
repo
that
has
a
bunch
of
our
smithy
interfaces,
those
are
for
actors
and
capability
providers,
and
also
we're
going
to
be
adding
the
the
internal
control
interface
that
we're
using
in
between
our
own
apps,
so
we're
using
smithy
idl
and
the
code
generation
from
that
for
those
within
a
day
or
so.
D
D
One
of
the
things
we're
a
little
behind
on
is
the
documentation,
so
we
wasmcloud.dev
is
a
little
out
of
date
there,
all
the
repos
don't
have
readme's
fleshed
out.
So
that's
one
of
the
next
things
we're
working
on
also
we're
putting
together
some
unit
tests
for
for
those
interfaces.
So
it's
another
another
thing
that
we
have,
that
we
didn't
really
have
do
a
great
job
in
the
dot
18
world,
so
keep
keep
an
eye
out
for
for
the
sample
code
and
documentation
over
the
next
week.
A
Any
just
calls
to
action
or
things
that
you
would
like
eyes
on
or
request
for
you
know
somebody
to
look
at
or
anything
like
that.
I
don't
know
just
I'll.
Have
some
of
those
I'll
have
some
of
the
some
of
those
next
week.
Okay,
super
all
right,
so
open
floor.
I
guess
kevin
or
brooks
anything
on
the
otp
release
that
you
want
to
highlight
as
we're
sort
of
marching
towards
completion
here
for
watson,
cloud
dot,
5.0.
A
All
right,
that's
great,
and
then
next
week
we'll
have
a
demonstration
of
the
new
javascript
runtime
for
wasmcloud,
which
we
have
flirted
with
for
a
while
and
calsheik
is
just
getting
wrapped
up.
We
did
post
a
poc
video
into
channel
if
you
are
interested
and
want
to
give
some
feedback
on
that.
It's
pretty
amazing
to
start
to
see
the
vision
come
together
around
march
of
the
run
times
and
and
so
forth.
If
there
are
no
other
updates
on
development,
I
guess
open
floor
here.