►
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
had
the
the
code
all
ready
to
go
on
my
linux
machine
and
since
I
can't
use
my
linux
machine
to
get
into
zoom,
I
don't
have
the
demo
code
on
my
mac.
If
I
had
like
another
hour
or
so
to
have
pre,
you
know
prepared
for
this
failure.
I
would
have
been
fine,
but
so
I
guess
next
week
I
will
probably
be
able
to
do
the
demo
and
maybe
demo,
setting
my
linux
machine
on
fire
so
either
way
it
ought
to
be
interesting
next
week.
C
A
A
A
A
A
So
what
I've
done
kind
of
before
this
call
is
gone
through
and
created
a
new
hello
project
from
the
hello
project
template
that's
in,
like
my
own
branch,
but
that'll
be
contributed
pretty
soon
and
then
push
this
up
to
github
in
this
repository
and
then
also
came
in
and
just
added
a
few
secrets
that
we'll
use
in
in
the
github
action.
You
know
my
issuer
key,
the
subject
key
for
a
hello
actor
and
then
my
github
personal
access.
Token.
A
All
these
things
are
kind
of
you
know
will
have
instructions
on
how
to
do
it's
not
too
long.
I
just
figured
I'd,
go
ahead
and
get
them
done
and
keep
the
demo
as
exciting
as
possible.
So
we
have
this
hello
actor
and
I'm
also
running
a
wasmcloud
host
on
my
local
machine.
Now,
one
of
the
bigger
problems
from
the
developer
experience
perspective
is
once
you
get
done
with
developing
on
your
local.
A
A
Now
we're,
including
a
release
action
with
our
project
templates
and
the
way
that
you
trigger
this
release.
Action
is
fairly
simple.
You
can
you
know
you
can
set
this
up,
however,
you
want,
but
I
have
it
set
up
so
that
if
I
push
a
tag
to
this
repository
with
the
name
of
the
actor,
you
know
hello
and
then
a
version.
A
A
What
happens
in
this
release?
Action
is,
we,
you
know,
install
wash.
We
build
and
sign
your
wasm
cloud
actor
with
your
issuer
and
subject
key
and
then
we
create
a
github
release,
so
it'll
be
easy
for
you
to
find
individual
releases
of
your
actor
and
release
it
to
to
github
cr,
so
in
one
fell
swoop
of
pushing
a
tag.
A
You
know
this
is
how
we
kind
of
do
it
for
the
wasm
cloud
assets
anyways
we're
just
pushing
to
our
azure
container
registry,
though
we
may
end
up
switching
to
this
in
the
future
you're
able
to
release
your
actor
to
an
oci
registry.
So
if
you
come
to
actions,
you
can
see
I've
been
doing
this
a
little
bit.
I
think
github
is
rate
limiting
me
because
I
keep
doing
this
over
and
over,
but
we
can
watch
this.
We
can
watch
this
happen.
A
You
know
the
build
takes
about
about
two
minutes,
but
while
this
is
going
on,
I
can
also
talk
through
the
build
action
that
we're,
including
this
one,
is
a
little
bit
simpler.
Any
time
you
create
a
pr
in
this
repository
to
main
it
will
build
and
check
your
actor
for
formatting
check
for
for
lintz,
which
that's
a
rust
specific
thing.
By
doing
this,
for,
like
a
tiny
go
or
an
assembly
script,
you
know,
as
we
add,
additional
language
support,
we'll
just
come
with
the
project
template.
A
So
this
this
makes
the
the
the
iteration
after
running
on
your
local
machine
a
lot
easier.
So
why
don't
I
go
ahead
and
show
you
what
that
looks
like
while
we
wait
for
this,
this
release
to
happen.
So
if
I
come
in
and
make
a
change
to
this
hello
world
actor,
you
know
previously,
it
would
say
hello
world,
you
know
we
can
say,
or
you
know
hello,
world
or
hello
name.
We
can
say
nice
to
have
you
or
something
like
that.
A
A
A
So
we'll
come
back
while
that
ends
up
getting,
kicked
off
and
check
out
our
release,
so
it
built
and
it
tested
just
fine.
The
next
step
is
going
to
be
releasing
to
github
cr
and
to
github
itself.
Just
you
know
the
the
github
release
isn't
something
that's
required.
I
just
find
it
as
a
nice
to
have
so
that
you
can
go
and
you
can
see
you
can
see
where
that's
been
released
to
and
then
you
also
have
a
wasn't
cloud
actor
artifact
that
comes
out
of
this.
If
you
wanted
to
do
any
debugging.
A
It
tells
us
a
tells
us
a
oci
url
that
we
can
use
to
access
this
actor
and
then
also
I
decided
to
dump
the
claims
information
here.
So
you
can
see.
I
may
have
the
a
different
key
here,
but
you
can
see
the
public
key
and
the
type
of
claims
that
this
actor
has,
and
this
is
really
useful
so
that
you
can
start
scripting.
You
know
what
the
actor
id
of
this
actor
is:
it's
just
kind
of
nice
to
nice
to
have
now
coming
back
to
coming
back
to
actually
accessing
this.
A
A
We
can
open
that
up
to
the
world
and
change
it
to
public
and
there's
no
need
for
you
to
do
this.
Are
you
gonna?
Let
me
type
it.
Okay,
there's
no
need
to
actually
do
this,
but
if
you
set
it
to
public
that
will
actually
let
you
come
into
a
a
wasn't
cloud
host
like
it
is
on
my
machine
and
start
in
hello,
2.0
and
start
this
actor
from
github
container
registry.
A
A
I
really
feel
like
this
simplifies
the
process
for
anybody
who
doesn't
want
to
set
up
a
container
container
registry
in
a
cloud
somewhere
and
make
sure
that
it
works
with
an
actor
and
the
the
automatically
built
in
you
know,
build
actions
for
printing
and
domain
really
helps.
You
enforce
a
some
some
good
practices
for
building
a
rust
actor.
D
Yes,
just
a
quick
question
since
when
we're
creating
the
template
with
you
know
wash
new,
does
it
make
sense
to
configure
like
linting,
as
maybe
pre-commit
hooks
on
the
local
client
side?
You
know
so
you
could
have
that
in
get.
Are
there
other
things
that
we
would
be
should
be
doing
as
best
practice
there
as
pre-commit
hooks
as
well.
A
I
think
one
really
good
thing
really
good
opportunity
with
rust
for
pre-commit
hooks
is
running
a
cargo
format.
You
know
running
a
build
running
a
test
or
even
running
clippy.
Sometimes
on
pre-commit
can
be
a
little
be
a
little
obstructive.
You
know
run
it
if
you
run
your
your
integration
test
or
something
it
takes.
A
You
five
minutes
to
do
a
commit
every
time,
it's
a
little,
it's
a
little
unwieldy,
but
the
running
the
cargo
format
on
like
a
pre-commit
hook,
especially
since
we
are
starting
that
git
repository,
we
probably
could
build
that
in
that
would
be
a
that
would
be
a
nice
I'm,
especially
for
rust.
I'm
not
aware
of
any
like
third-party
formatter.
That
would
be
preferred.
I
guess
we
could
always
turn
that
off
with
like
a
little
feature,
flag.
D
A
Just
one
thing
like
I
said:
I
really
think
that
github
is
rate
limiting
me,
because
I
was
doing
all
this
testing
and
wasn't
getting
any
delays.
But
now
it
takes
maybe
a
minute
for
these
actions
to
kick
off
just
because
I
keep
doing
it
over
and
over.
But
in
this
pr,
where
you
know
we
made
that
really
small
commit.
You
can
see
that
all
all
checks
have
passed.
If
you
look
at
the
checks,
we
are
checking
the
formatting
building,
the
actor
checking
for
lints
and
and
all
those
things.
A
B
A
Yeah,
thank
you
that
that
is
something
that
you
know.
I
wanted
to
include
the
things
that
I
feel
like
we've
been
wanting
with
our
own
pipelines
for
a
while,
which
is
showing
the
oci
reference
that
you're
pulling
from
and
that
you
can
pull
from,
and
then
the
claims
information
so
glad
that
I
got
that
in
one
other
win
that
I
thought
would
be
fun
to
share
was
you
know.
A
A
B
D
D
I
100
get
that,
but
I
in
that
case
I'm
pulling
the
artifact
down
right
using
wash
and
then
pulling
that
metadata
out.
It
would
it
be
helpful,
and
this
is
a
question
to
pull
be
able
to
pull.
You
know,
pull
the
hash
of
the
of
the
file
out.
First,
you
know
maybe
to
like
set
up
a
script
or
something
like
that.
I
don't
know
I'm
just
trying
to
think
about.
B
C
A
You
one
thing
one
thing
that
we
always
could
do
with
this
action.
I
don't
know
if
I
showed
this
actually,
but
under
the
release
under
assets
we
also
attached
the
hello
or
the
the
wasm
file.
We
could
also
dump
the
claims
to
like
a
json
file
and
then
attach
it
here
under
assets.
If
you,
you
know,
wanted
to
come
into
this
release
and
instead
of
it
may
be,
you
know
the
the
scripting
capability
of
that
may
be
a
little
bit
clunky,
but
you
could
always
pull
the
claims
down.
A
A
A
B
A
Cool
well,
after
that,
I
have,
unless
anybody
has
any
other
questions
for
the
for
the
demo.
I
have
a
couple
of
fun
call
outs
for
next
week
and
starting
actually
this
weekend,
which
is
kubecon
eu.
We
have
a
couple
of
great
talks
and
then
taylor
liam
and
I
will
actually
be
in
valencia,
for
anybody
who
comes
by
please
come
see
us
at
our
booth,
we'll
be
there
most
of
the
time,
except
for
pretty
much,
except
for
when
we're
giving
our
talk.
A
But
we
also
have
you
know
other
than
just
cosmonic
and
wasn't
cloud
people
we
have
some
exciting
things
going
on
christoph
with
bmw
is
going
to
be
giving
a
talk
at
cloud
native
rejects,
and
it
doesn't
look
like
the
whole.
The
schedule
is
posted
like
if
I
click
on
talks,
it
doesn't
show
me
specific
ones
but
he'll
be
presenting
on
saturday.
A
I
believe
in
this
second
block,
the
the
2pm
block
and
liam
you
can
correct
me
if
I'm
I'm
wrong
there,
but
if
anybody's
going
to
be
attending
cloud
native
rejects
virtually
please
keep
an
eye
out
for
that.
That's
going
to
be
our
kind
of
the
culmination
of
our
machine
learning
work
with
with
kristoff
and
bmw,
which
is
really
exciting.
A
After
that
we
have
the
kubecon
cloud
native
con
eu,
where
taylor
and
I
are
going
to
be
giving
a
talk
on
wednesday.
The
title
is
disrupting
the
downtime
continuum,
which
is
not
only
fun,
but
the
talk
is
going
to
be
a
lot
of
fun
too.
So
please
come
check
that
out.
If
you're
going
to
be
there
or
check
it
out
virtually
if
you
have
a
ticket,
it
should
be
super
fun
and
not
just
you
know,
taylor
and
I
giving
a
talk.
A
We
also
have
office
hours,
but
then
on
cloud
native
wasm
day,
which
is
like
a
co-located
event.
It's
on
monday,
so
kind
of
the
first
day
of
the
conference.
We
have
three
different
talks
that
are
going
to
be
talking
about,
wasn't
cloud
which
is
really
exciting.
One
from
steve
sanderson
is
going
to
be
talking
about
webassembly
and
net
in
general,
but
we'll
also
talk
about
wasn't
cloud
as
well
in
his
talk
and
then
we
also
have
alan
poon
who's
going
to
be
doing
a
lightning
talk
on.
A
Wasn't
cloud
and
the
bevy
ecs
the
the
game
engine
which
is
really
exciting?
This
is
one
that
I'm
personally
looking
forward
to
a
lot
and
some
of
the
people
at
adobe,
colin
murphy
and
sean
who
are
going
to
be
talking
about
webassembly,
not
only
just
in
the
browser,
which
is
how
they,
what
they
use
for
things
like
photoshop
in
the
browser,
but
also
on
the
server
side,
with
wasmcloud
as
a
heavy
part
of
their
their
presentation
and
demo.
A
Okay,
just
curious:
it's
you
know
it's
out
there.
I'm
the
in
person
conference
again
is
is
exciting
that
those
are
those
are
coming
back.
Hopefully,
everybody
is
is
safe
and
it
can
all
be
a
good
time
all
right.
That's
what
I
had
for
community
call-outs,
let's
see
liam
or
kevin,
do
you
have
anything
else
that
we
want
to
call
out
to
everybody
here.
D
D
E
That's
fun
yeah,
so
we've
been
talking
about
this
a
while
and
we're
we've.
We've
done
some
work
on
getting
the
the
trainings
out
there
and
and
operational
and
and
one
of
the
things
we
had
to
do
in
order
to
capture
like
user
metrics
was,
you
know,
wrap
it
so
that
we
could
like
know
who
was
using
our
tools
and
and
make
sure
that
they
were
working
and
all
that
stuff.
So
it's
live
right
now.
I
wouldn't
post
it
to
twitter.
E
Just
yet,
maybe
give
me
another
week
before
we
start
sharing
it
super
wide.
But
if
you,
if
you
go
to
labs.cosmonic.com,
we
can
start
to
see
our
the
the
trainings
as
they
start
to
roll
out,
and
you
know
very
simple
interface
right,
you'll
you'll
meet
you'll.
Get
this
little
smiley
face.
That's
green!
E
I
don't
know
why
it's
green,
but
if
you,
if
you
log
in
you
know
you
get
this
little
button
and
when
we
start,
we
start
seeing
all
our
trainings
here
and-
and
we
can
go
through-
and
you
know
and
experience
that,
but
one
of
the
cool
things
about
this
is
and
why
it
matters
to
the
community
is
eventually
all
the
contents.
That's
backing.
This
will
be
in
a
repository
somewhere
and
what's
cool
is
as
simple
as
there's
a
wash
intro
as
well,
and
you
can
see
right
now.
Currently,
it's
it's.
E
And
then
without
having
to
well
it
takes
about
a
minute
and
then
without
having
to
update
the
platform,
we'll
see
the
wash
intro
start
there
and
why
that's
cool
is
we're
going
to
wrap
this
in
a
github
action
and
then
we
can
start
doing
like
community
driven
trainings
on
the
platform,
which
will
be
pretty
neat,
hey,
look
at
there
and
see.
This
is
why
we're
not
going
to
share
with
too
many
people,
because
css
is
still
a
thing.
I've
got
to
figure
out
so
yeah.
E
D
That's
awesome,
jordan.
I
went
through
I'm
going
to
going
through
the
the
training
right
now
and
I've
got
a
round
of
feedback
and
I'll
try
to
maybe
submit
some
of
that
as
pull
requests
right
to
instruct.
So
we
can
maybe
get
those
announced
for
next
week
is
what
I'd
love
if
we've
got
an
easy
way
to
help.
People
get
started,
and
you
know
start
to
start
to
use
and
learn
about
the
tools.
It
could
be
something
we
could
even
do
right
from
the
booth
next
week
at
kubecon.
Yes,.
E
C
D
D
You
know
a
quick
first
pass
to
get
something
in
it's
hard
to
edit
a
blank
page
so
to
get
something
down,
so
we
can
iterate
forward
from
there,
but
I
think
even
the
first
round
of
edits
all
do
a
lot
of
it
we'll
be
adding
in
some
pictures
and
some
logical
constructs
and
making
sure
that
we're
helping
people
to
understand
what
we're
driving
with
the
separation
of
you
know
boilerplate
and
business
logic.
You
know
the
separation
of
those
two
things
for
your
apps.
D
A
A
Okay,
yeah,
we
have
some.
Let's
see,
I
don't
know
if
that's
actually
exactly
public
or
not,
but
we
have
some
yeah.
That
is
public.
We
have
some
of
the
wasmcloud
logos
in
like
our
branding
repo.
I
just
put
it
in
the
chat,
but
then
some
of
the
logos
from
like
our
powerpoint
or
like
our
presentations
that
we
do
for
like
the
wasn't
cloud
architecture
we'll
have
to
try
to
get
those
out
as
well.
C
D
A
Let's
see,
I
think
that
that
is
all
that
I
had
for
for
demos
and
community
callouts
that
so
that's
all
that
I've
got
anybody
else
have
anything.
Otherwise
we
can
just
we
can
just
hang
around,
we
can
stop
recording
and
then
you
know
do
what
we
normally
do,
which
is
come
up
with
a
super
fun
topic
as
soon
as
we
stop
recording.