-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Add a section describing how to use wasmtime Rust SDK to consume components. #87
Comments
This would be super handy. @Mossaka @kate-goldenring do you think such an example should re-use the calculator from the tutorial? Couple of weeks ago I built an sample that demonstrates how one could build an agnostic plugin-mechanism using the component model. Basically, it is a super simple contract with guest implementations in Rust and JS (in my sample). The host application is a simple Rust CLI app, which iterates over WDYT? |
Hey @Mossaka it seems like in the current version of the component-model docs, this issue is pretty much solved 🎉 thanks to all the maintainers that have been putting in work over what is now (almost) a year! Is there anything else you wanted concretely built into the docs from this issue? |
The plugin and |
I wrote a bit on Wasmtime host implementation which is in the Rust pages for now, but some people felt that, in the long term, content like that should move to the Wasmtime book. (I don't have strong feelings one way or the other.) |
That makes more sense, actually! Happy to close this issue now |
Currently the docs has a section for wasmtime and it only describes how to run a command component using
wasmtime run
. Another helpful section could be added to describe how to use wasmtime SDKs to run components programmatically. A good starting point would be the wasmtime rust SDK withcomponent-model
feature on.The text was updated successfully, but these errors were encountered: