ritesh089
ritesh089
I like the option of shared manifests . Isn't the naming confusing though ? The provider is being referred to as a component in this shared manifest . ``` manifest:...
The components are usually written in separate repositories and the great thing about the component model is reuse. The example currently shown in the docs uses a single wit and...
Thanks @kate-goldenring , I will update the PR by updating the tutorial docs and overwrite the tutorial directory. Do you think it makes sense to keep a go component (sub)...
@FrankReh , I didnt understand this part : ```although I'll admit I changed 'sub' to be Rust``` I think i will change this PR to draft for reference and open...
Yes i have enabled debug logs . Host traces dont show up for me .
> If this works, should we revert #2386 in this PR? Done
> Hey @ritesh089 this looks awesome -- would you mind changing the `scope` in your commit to `examples`? Otherwise this looks perfect -- though I'll defer to @brooksmtownsend since he's...
@vados-cosmonic , Can you provide an example configuration on how to set tracing endpoint for http client and http server provider?
The lightweight nature of Wasm components in WasmCloud allows us to host a large number of components in a wasmHost . I dont think it should maintain the limitation of...
> So when linking to the builtin provider, would it expect to have config like `DOMAINS=*.example.com,example.com`? I think I'm ok with that! Actually the domain name doesnt need to change...