Documentation site for wasmCloud.dev
Home Page: https://wasmcloud.dev
The previous home for wasmCloud documentation! After our documentation epic, all documentation source code is now served in the wasmcloud.com-dev repository and is hosted at https://wasmcloud.com. This was done in the interest of keeping all of our content in one place.
If you have any links that refer to https://wasmcloud.dev, they will automatically redirect to https://wasmcloud.com.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://youtu.be/-CT7YyO6vn4
Tweet:
The customizing the actor section in the documentation mentions using the command make update but this is in fact commented out in the actor.mk file.
https://wasmcloud.dev/reference/refapps/ should be written and submitted to the docsite to complete the reference section.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://youtu.be/kuOqbaIhSy0
Tweet:
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://www.youtube.com/watch?v=1JLJ5LoFeDw&list=PL25tdRgIAXSseiyM1zlSG-EH16qOOsQSA&index=47
Tweet:
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video:
Tweet:
TinyGo Code Generation Demo
Back from WasmDay Updates
wasmCloud Blog Post Released
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video:
Tweet:
Updated Pet Clinic Demo - UI Actor
Create Your First Actor Demo
GHCR Integration
TinyGo Actor Demo
Community Announcements
New WADM Documentation/RFC
In the actor documentation the command for using wash to create a link looks like this:
wash ctl link ACTOR_ID VAG3QITQQ2ODAOWB5TTQSDJ53XK3SHBEIFNK4AYJ5RKAX2UNSCAPHA5M wasmcloud:httpserver address=0.0.0.0:8087
It should have a put subcommand like this:
wash ctl link put ACTOR_ID VAG3QITQQ2ODAOWB5TTQSDJ53XK3SHBEIFNK4AYJ5RKAX2UNSCAPHA5M wasmcloud:httpserver address=0.0.0.0:8087
Too many words, compared to other pages in docs
There are a few different ways to shutdown a wasmCloud host. If launched from the distillery release, it should be done with ./bin/wasmcloud_host stop. If launched with iex, it can either be closed with CTRL+c a, CTRL+c CTRL+c, or with HostCore.Host.shutdown. The HostCore.Host.shutdown is the preferred method as it allows providers to cleanly shutdown.
We should add this to our documentation to avoid scenarios where providers are dangling (the fix is to find providers, I usually do ps aux | grep VA to find the process, and then kill <pid>
The list of all the host configuration variables should contain the OCI_REGISTRY_USER and OCI_REGISTRY_PASSWORD variables so users can figure out how to set up their host to talk to a private registry
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://youtu.be/Wih95FAfQz4
Tweet:
https://wasmcloud.dev/reference/
This page should be updated to at least remove the boilerplate and point to the next reference page.
Some things that should be in this new documentation:
This new documentation should have a step-by-step guide to creating a lattice of 3 hosts, illustrating all of the web UI/CLI tool commands required to manage this.
Have you run into an error with wasmCloud? Was it difficult to track down the source of the problem after you saw an error in the wasmCloud host logs? Well this thread is for you!
Please leave feedback on any scenarios that you've run into, with as much detail that you can remember. Bonus points if this is an issue that you resolved on your own. We'd love to improve our documentation troubleshooting guides to include common use cases and your feedback can make that even better than it is today.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video:
Tweet:
Our documentation covers the local case very well, but when we get into the following domains we could use more information in the dev docs.
Some recent changes to wasmbus/libssl dependencies warrants a sweep of our OCI references
if a provider health check fails, will it still get a shutdown message before its process is terminated?
how long can a provider take to shutdown before it's process is killed?
what is the sequence of operations & messages for restarting a failed actor or provider? (Including link additions/removals, etc)
what is the relative timing between a failing provider shutdown and new provider starting? Can there be periods of time when they are both running? Can there be periods of time when neither are running?
Are there plans in the roadmap, or other ideas, for improving the health check protocols and processes?
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 wasmcloud:httpserver \
--name hello --ver 0.1.2 --rev 0 \
--call-alias wasmcloud_example_hello \
--destination build/hello_s.wasm
The \ used for line continuation doesn't work in windows 10 Powershell, so the command make fails. If you start bash (or the shell from the "Git bash" package), and then run make, it works.
In the App Development section of our documentation, developers would benefit greatly from a "commonly seen errors" section.
This section could provide common errors encountered during wasmcloud actor development. Some that come to mind are:
calling an actor)Malformed response from actorA document like this would not attempt to be a comprehensive resource for all actor errors. What this would be useful for is to give developers a starting off point with common causes of these errors, and if they have not made use of the logging provider then a resource that points them to use that, as stdout is not viewable from an actor module.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://youtu.be/9jrKf2VCQmI
Tweet:
Thanks for the recent update of the wasmcloud.dev site. Much appreciated.
It would be great with some rudimentary documentation (perhaps through examples) on wapc and how to add new language bindings. In particular I am interesting in adding C++ as an actor language.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://www.youtube.com/watch?v=WuKXL25GHns&list=PL25tdRgIAXSseiyM1zlSG-EH16qOOsQSA&index=46
Tweet:
wasmcloud.dev should not participate in Google's FloC.
Reference: Google's FLoC is a Terrible Idea
Running wasmCloud in a Docker container works great, though for hot reloading we require access to the filesystem to watch the actor. When running in Docker, the filesystem is not the user's filesystem, so attempts to run an actor from the filesystem will fail with an enoent error.
build/ directory to a directory on the container, then hot reloading should function as intended. This should be verified to work on different operating systems (Docker Desktop is different on Mac/Linux/Windows)We have full support for linux and macos, but from our recent discoveries we know that we don't support loading native capability providers as shared objects on Windows. (.dll) (wasmCloud/wasmCloud#60)
We should mention this in our documentation to prevent users on Windows (not WSL) running into issues.
Ui ads <span class="copy-to-clipboard">copy</span> element to <code> tags when navigating via links (usually one but sometimes more than one) and these buttons get multiplied when using forward and backward buttons and eventually page becomes unresponsive.
It happens in Firefox 86.0 (64-bit) and Chromium Version 89.0.4389.90 (Official Build) snap (64-bit).
Here is an image and screen captures. At the end of the second video, you can see console log. I also added parts of it below:
DevTools failed to load SourceMap: Could not load content for https://wasmcloud.dev/plugins/bootstrap/bootstrap.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
You are loading Turbolinks from a <script> element inside the <body> element. This is probably not what you meant to do!
Load your application’s JavaScript bundle inside the <head> element instead. <script> elements in <body> are evaluated with each page change.
For more information, see: https://github.com/turbolinks/turbolinks#working-with-script-elements
——
Suppress this warning by adding a `data-turbolinks-suppress-warning` attribute to: <script src="https://wasmcloud.dev/plugins/turbolinks/turbolinks.js"></script>
(anonymous) @ turbolinks.js:6
(anonymous) @ turbolinks.js:6
(anonymous) @ turbolinks.js:6
(anonymous) @ turbolinks.js:6
(anonymous) @ turbolinks.js:6
In the current site when we place content inside a tab partial, it uses a specific style and creates a div. What we can't do is use the triple-backtick to enable syntax highlighting or other goodies inside that content. Right now, we're forced to use the preformatted style sheet. Further, we can't even include blank lines inside the tab because it screws up the formatting.
When this is done and working, we should be able to have tabs that include syntax highlighted code samples that support multiple blank lines and potentially other content above and below the sample.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video:
Tweet:
https://wasmcloud.dev/reference/lattice/architecture/ should be written and submitted to the docsite to complete the reference section.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video: https://youtu.be/FbuFpi8naRk
Tweet:
There a few small inconsistencies in interface and crate names in the provider tutorial and examples which makes the experience bumpy. It would also be good to have some explanation as to what till fill in when doing the wash new interface generation.
https://wasmcloud.dev/app-dev/secure/ should be written and submitted to the docsite to complete the reference section.
Hot reloading depends on one package per-OS to be installed, we should note this in the hot reloading section
We can link to https://github.com/falood/file_system#system-support because that section individually links to the proper packages.
Fully document the protocols used by lattice:
These should be documented in a language agnostic fashion in an appendix on wasmcloud.dev
This is the section of the docs right beneath "installation", and this is in most cases going to be a developer's first exposure to wasmCloud. This section of the docs should walk the developer through their first experience with wash by having them fire up the repl and go through the simple demo script - start an actor, start a provider, link the actor to the provider, curl the endpoint, and then finish up with a taste for advanced techniques by doing a direct call on the actor.
The curl commands as they exist in the docs will not work on Windows (as it isn't actually curl it is calling). Curl commands need a flag and all addresses prefaced by http. Any examples with curl should also have a powershell specific example where the command looks like this:
curl -UseBasicParsing http://<rest of url>
I am following the tutorials for new actors and there are several places where the site does not match the code. I will fork and try to make a PR out of this.
https://wasmcloud.dev/app-dev/secure/ should be written and submitted to the docsite to complete the reference section.
On page Customizing the actor, the following query statements:
curl 'localhost:8087/?name=Alice,msg=hello'
curl 'localhost:8087/?name=Bob,msg=bye'
curl 'localhost:8087/?name=Carol,msg=hey'
are wrong and should be:
curl 'localhost:8087/?name=Alice&msg=hello'
curl 'localhost:8087/?name=Bob&msg=bye'
curl 'localhost:8087/?name=Carol&msg=hey'
In the create provider section: https://wasmcloud.dev/app-dev/create-provider/, there are some outdated references to widl files, interfaces, and no mention of https://github.com/wasmCloud/new-provider-template which should be the de-facto way to create a rust provider.
As mentioned by the community, some tutorials (specifically https://www.wasmcloud.dev/app-dev/create-actor/) we don't mention the prerequisite of running NATS. wash as of 0.2.0 will alert the user that it's required, but we should at least mention the requirement while we work on a tutorial that does not require NATS.
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video:
Tweet:
wash 0.10.0 Released (breaking change)
Community Callout
"Running Your UI on wasmCloud" Blog Post
TinyGo Actor Support
Future CodeGen Discussion
This issue should only be closed by a commit to the site with the minutes and
artifacts for easy referencing
YouTube Video:
Tweet:
GHCR + Github Action Demo
wasmCloud @ KubeCon Updates
wasmCloud Training Site Released
make update command either needs to be commented back in for the common makefile, or we need to provide a live update command that can be run manually. I'd lean towards the former, as we should provide the make update functionalityWe could potentially mitigate 1 if we can find a way to serve the localhost registry over https, but that would only be worth it if we can easily provide that as a part of the docker compose, not worth it if multiple certificates are required.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.