-
### Affected project(s)
- [ ] documentation
- [ ] examples
- [ ] wasmCloud host
- [ ] wasmCloud CLI (wash)
- [X] wasmCloud dashboard UI (washboard)
- [ ] capability providers
- [ ] provider b…
-
### Application contact emails
danielle@fermyon.com, c.voigt@reply.de, fcastelli@suse.com, jiazho@microsoft.com
### Project Summary
SpinKube is an open source platform for efficiently running (cont…
-
While trying to implement https://github.com/wasmCloud/wasmCloud/issues/497, we discovered that shared types (defined in an `interface`) bubble up as imports to the top level when composing. For examp…
-
### Affected project(s)
- [ ] documentation
- [ ] examples
- [ ] wasmCloud host
- [X] wasmCloud CLI (wash)
- [ ] wasmCloud dashboard UI (washboard)
- [ ] capability providers
- [ ] provider bindgen
-…
-
This proposal is to detail a suggested overhaul of the developer experience for those writing components for wasmCloud (although this experience would technically work for anyone working on components…
-
-
the makefiles in the examples project use mult-line commands such as
the `wash claims sign` command:
```
wash claims sign target/wasm32-unknown-unknown/release/hello.wasm \
-c wasmclou…
-
wasmcloud.dev should not participate in Google's FloC.
Reference: [Google's FLoC is a Terrible Idea](https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea)
-
https://wasmcloud.dev/reference/lattice/architecture/ should be written and submitted to the docsite to complete the reference section.
-
### Affected project(s)
- [X] wasmCloud host
### Describe the solution you'd like
It'd be neat to have the host determine the interfaces of the components (providers might be a little harder)…