wasmCloud · lachieh · Jan 16, 2025 · Jan 15, 2025 · Jan 15, 2025 · Jan 15, 2025
@@ -1,5 +1,5 @@
 ---
-title: 'Deploying wasmCloud Actors from Github Packages'
+title: 'Deploying wasmCloud Actors from GitHub Packages'
 image: './images/github-packages.png'
 date: "2022-05-23"
 authors: [brooksmtownsend]

@@ -24,7 +24,7 @@ This function is _"pure"_. For every input of `x` there is only one output. In m
 
 Unfortunately, the second we expand our code beyond the realm of "hello world", it becomes more and more difficult to maintain purity. Our code needs to interact with the world, and it often does so in messy, unpredictable ways. Even if it isn't messy, we frequently see functions where the answer is only predictable for a short period of time.
 
-Let's take a look at this (psuedocode) function from a hypothetical bank back-end that handles an international withdrawal from a customer's account:
+Let's take a look at this (pseudocode) function from a hypothetical bank back-end that handles an international withdrawal from a customer's account:
 
 ```
 internationalWithdrawal account amount localCurrency =

@@ -91,7 +91,7 @@ Here are what the interfaces look like:
 
 ```
 // These are importing some common types that you see in the receive function signature. See the
-// actual code on Github if you are curious what these types look like
+// actual code on GitHub if you are curious what these types look like
 use * from error-type
 use * from wasmbus-common
 

@@ -13,7 +13,7 @@ The world of WebAssembly (Wasm) runtimes has evolved quickly over the last coupl
 
 {/* truncate */}
 
-As part of the continued effort to align wasmCloud with WASI standards and the component model, we've made a considered shift to Wasmtime for a couple of important reasons. Firsly, Wasmtime lives at the cutting edge of the Wasm ecosystem. It is the runtime used in a slew of major projects, and has been adopted by [Shopify, Fastly, Fermyon, Microsoft, and more](https://bytecodealliance.org/articles/wasmtime-1-0-fast-safe-and-production-ready). We're incredibly lucky to be able to participate with them as our friends and teammates in the Bytecode Alliance, where the Wasmtime project is hosted.
+As part of the continued effort to align wasmCloud with WASI standards and the component model, we've made a considered shift to Wasmtime for a couple of important reasons. Firstly, Wasmtime lives at the cutting edge of the Wasm ecosystem. It is the runtime used in a slew of major projects, and has been adopted by [Shopify, Fastly, Fermyon, Microsoft, and more](https://bytecodealliance.org/articles/wasmtime-1-0-fast-safe-and-production-ready). We're incredibly lucky to be able to participate with them as our friends and teammates in the Bytecode Alliance, where the Wasmtime project is hosted.
 
 With flexibility and choice in mind, we've also re-architected the way that we pull in Wasmtime so that we can use _other_ types of runtimes that work well in tiny places. We haven't started that work yet, but we've been sure to design for it.
 

@@ -38,7 +38,7 @@ For the latest and greatest in Wasm standards and innovation, and a practical gu
 
 ## [Pathfinder to GPU Offload in WASM](https://www.youtube.com/watch?v=3G9kANTKjmQ&list=PLj6h78yzYM2MQteKoXxICTWiUdZYEw6RI&index=4)—Atanas Atanasov & Aaron Dorney, Intel
 
-It's an exciting time for companies at the cutting edge of embedded systems and devices. Atanas and Aaron's talk gives a sense of the opportunity companies like Intel are identifying in bringing Wasm to embedded systems. Speficially, this demo-laden talk questions why we would want GPU offload in the Wasm ecosystem and takes a closer look at the tools available right now to achieve this.
+It's an exciting time for companies at the cutting edge of embedded systems and devices. Atanas and Aaron's talk gives a sense of the opportunity companies like Intel are identifying in bringing Wasm to embedded systems. Specifically, this demo-laden talk questions why we would want GPU offload in the Wasm ecosystem and takes a closer look at the tools available right now to achieve this.
 
 According to Adanas and Aaron, there are two major use cases for GPU offload in Wasm. The first is when working with AI/ML as a service, the second rendering as a service. This makes sense when considering the associated deployment targets; standalone desktop apps, cloud apps in resource-constrained environments, applications running in browsers and node js. All these environments rely on low-latency and high performance. This is something that containers struggle with—as the team describes, the overhead of spinning up a container is not conducive to these use cases.
 

@@ -65,7 +65,7 @@ Since wasmCloud supports custom interfaces written with the community-standard i
 
 - You might also want to see our [**blog on why WASI 0.2 is such a big deal**](/blog/wasi-preview-2-officially-launches).
 
-- If you're new to components, WASI, and the wider WebAssembly ecosystem, check out our [**Concepts documention**](/docs/concepts) to get up to speed&mdash;the [**Components**](/docs/concepts/components) page is a great place to start.
+- If you're new to components, WASI, and the wider WebAssembly ecosystem, check out our [**Concepts documentation**](/docs/concepts) to get up to speed&mdash;the [**Components**](/docs/concepts/components) page is a great place to start.
 
 ## Completely OTEL observable
 

@@ -138,7 +138,7 @@ world root {
   export example:pong/pingpong;
 }
 ```
-The new component exports `pingpong` but no longer imports `wasi:cli/environment`&mdash;that requirement has been abstracted awat. If we run this component on wasmCloud, the host will be able to satisfy the `random` import&mdash;it will simply require another component to invoke it via the `pingpong` interface. 
+The new component exports `pingpong` but no longer imports `wasi:cli/environment`&mdash;that requirement has been abstracted away. If we run this component on wasmCloud, the host will be able to satisfy the `random` import&mdash;it will simply require another component to invoke it via the `pingpong` interface. 
 
 In the `http-hello2` directory is a modified `http-hello-world` component that imports the `pingpong` interface and calls for a string from `pong` to append to the hello world message. Navigate to that directory and build the component.
 

@@ -27,7 +27,7 @@ Capability providers using the latest provider SDK will now be able to [subscrib
 
 Capability providers implementing `wrpc:blobstore` are **strongly recommended** to update to the latest version (`0.2.0`) in order to take advantage of blobstore async streaming. The host will remain backwards compatible with `wrpc:[email protected]` for at least a minor release.
 
-See https://github.com/wasmCloud/wasmCloud/pull/2779 for three implementation examples (Fileystem, Amazon S3, and Azure Blobstore) to see the best path for upgrading. We’ve updated and released each of these providers, so make sure to update your wadm manifests when possible:
+See https://github.com/wasmCloud/wasmCloud/pull/2779 for three implementation examples (Filesystem, Amazon S3, and Azure Blobstore) to see the best path for upgrading. We’ve updated and released each of these providers, so make sure to update your wadm manifests when possible:
 
 - [ghcr.io/wasmcloud/blobstore-azure:0.4.0](http://ghcr.io/wasmcloud/blobstore-azure:0.3.0)
 - [ghcr.io/wasmcloud/blobstore-fs:0.9.0](http://ghcr.io/wasmcloud/blobstore-fs:0.9.0)

@@ -33,7 +33,7 @@ date: 2023-02-01
 - Been keen to get started since Slack started discussing testing actors with Dagger.
 - Focused on end-to-end integration tests rather than unit tests right now.
 - Also working on a way to mock the lattice which he'll use for unit tests eventually.
-- Dagger allows you to take your CI/CD pipelines and run them identically, locally as you would in Github action or anywhere else.
+- Dagger allows you to take your CI/CD pipelines and run them identically, locally as you would in GitHub action or anywhere else.
 - This is pretty cool as one of the biggest pain points occurs when testing code at work, then trying to test later at home or in github - these are completely different test structures which causes confusion.
 - Demo shows wash new echo actor - build, sign, inspect, name and then call.
 - What's really cool is a call test on the actor which allows me to do some sanity checking. I.e. that it's functioning.

@@ -84,7 +84,7 @@ date: 2023-05-10
     - It'd be more unpredictable which would be an even bigger problem than security.
     - Link names can't change since the actor needs them
 - Brooks: It's interesting
-  - Jochen: Is this a limitation of NATS or a chosen path? since it can only receive on single paht but listen on a \*?
+  - Jochen: Is this a limitation of NATS or a chosen path? since it can only receive on single path but listen on a \*?
   - Brooks: It's more of a chosen path -- we use a different links (frotend and backend) to get around that, so we're flexible in routing.
 - Brooks: We're trying to find a way for linking to be more natural
   - Most of the time there's not even configuration required (ex. HTTP Client is just making outbound requests, versus HTTP Server which _might_ need a port to listen on)

@@ -18,7 +18,7 @@ date: 2023-06-21
 - We had a problem with the observability of wasmCloud capability providers. In particular, official capability providers and example actors that we publish to Azure Container Registry.
 - The issue? Azure CR does not support unauthenticated dynamic content discovery so it's tricky to track versions.
 - We had a workaround - the Capability Provider Repo and shields.io badges. We've been using a dynamic json badge - using their API to provide a custom payload.
-- Issue: Readme in Github - markdown does not have ability to run customer code - no auto-update.
+- Issue: Readme in GitHub - markdown does not have ability to run customer code - no auto-update.
 - Last week we ran with an idea proposed by Jordan: capitalizing on the Azure Container Registry webhook - allows you to call version data after it pushes a new image version to Azure CR.
 - From here we can see the latest information and use the Key-Value contract to save this information in the KV store.
 - We also set up categories in order to fetch all the official capability provider data - name, OCI URL, actors.

@@ -19,7 +19,7 @@ date: 2023-07-12
 - Starting point: identify in wit what wasmcloud's RPCbus looks like - [PR in wasmCloud interfaces](https://github.com/wasmCloud/interfaces/pull/116).
 - If you were to pull up the smithy version of our core contract it maps pretty much 1:1 (with a few possible future exceptions).
 - With the provider SDK in Go we can convert any wasmCloud interfaces on Tiny Go into core Go interfaces.
-- If we were to take the Bytecode Allliance wit-bindgen binary in the Github repo and run it over a wit file we would be able to replace smithy.
+- If we were to take the Bytecode Allliance wit-bindgen binary in the GitHub repo and run it over a wit file we would be able to replace smithy.
 - Demo is still work in progress but it funnels in 2 parts:
   - Provider and an actor running in wasmCloud with no more smithy IDL interface pieces generated.
   - You can see in NATS that the 30-second health check is running - ping pong provider running/ We can query the actor (you say ping, we say pong).

@@ -39,7 +39,7 @@ date: 2023-08-02
 - This is an exciting time as we have componentized wasmCloud in line with these new standard and the soon-to-be-finalized Component Model.
 - As we move towards WasmCon in September, stay tuned for more detail on the wasmCloud blog.
 - As you know any open source project is going through constant change but we now have a high level wasmCloud roadmap. Currently in review by docs maintainers.
-- Find the relevant pages on our [docs site](https://wasmcloud.com/docs/roadmap). Also a continously updated [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/3).
+- Find the relevant pages on our [docs site](https://wasmcloud.com/docs/roadmap). Also a continuously updated [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/3).
 - Loosely pinned to q3 and q4 of 2023.
 
 ### Goals:

@@ -51,7 +51,7 @@ date: 2023-09-20
   - Rust Host lost some of that introspection.
   - Info on number of actors providers invocations that have a particular provider or actor.
   - Interesting summary stats around specific resource usage: so we can more accurately scale actors up and down.
-  - Provider exposing metrics - counter for number of 500s/400s is pretty common. We want to be able to do the same thing in wasmCoud.
+  - Provider exposing metrics - counter for number of 500s/400s is pretty common. We want to be able to do the same thing in wasmCloud.
   - Some work to do to decide how, but this is where we're leaning.
   - [Observability and metrics RFC](https://github.com/wasmCloud/wasmCloud/issues/664) - please get involved if you have expertise - we're excited to hear your opinions and experiences.
   - Check out the recording for the full discussion.

@@ -35,7 +35,7 @@ Welcome to our new community members Marcelo Lopez and Mfon! 🎉
 
 - Note: wasmCloud processes are limited by executing for 2 seconds by default, overridable by the `WASMCLOUD_RPC_TIMEOUT_MS` variable.
 - Recommended additional reading: [Dealing with the Diabolical Distributed Deadline Dilemma](https://kevinhoffman.blog/post/distributed_deadlines/)
-- Timeout is usually configured at runtime. Whatever value you state, that's how long wasmCloud will allow a chain to execute - nested timout.
+- Timeout is usually configured at runtime. Whatever value you state, that's how long wasmCloud will allow a chain to execute - nested timeout.
 - wasmCloud is a distributed system capable of running on one or many machines. As such, it's hard to tell whether an operation is taking a long time because it's timing out versus a process that will never finish because it has made requests that it will never return.
 - Example: downloading a file can take an arbitrary amount of time depending on the quality of the network, how big the file is etc. We limit execution types, and infinite timeout, with the timeout kill switch.
 - Discussion

@@ -28,7 +28,7 @@ date: 2023-10-04
 ### DISCUSSION: Hacktoberfest! 🎃
 
 - 10th year of Digital Ocean's event. [Hacktoberfest.com](http://Hacktoberfest.com) brings together open source maintainers who are eligible to designate their open source project for Hacktoberfest.
-- All you need to do is to close or have 4 approved pull requests on Github or GitLab.
+- All you need to do is to close or have 4 approved pull requests on GitHub or GitLab.
 - One you have this, DigitalOcean will plant a tree on your behalf and send you a nice virtual badge.
 - All you need to do if you want to partake is sign up on the website.
 - On the wasmCloud side we'll designate our good issues and some stretch issues with the goal to lower the barrier to people are getting started in Wasm.

@@ -46,7 +46,7 @@ date: 2023-10-18
 - We went over the [kvcounter demo](https://github.com/wasmCloud/examples/tree/main/actor/kvcounter-wasmcon2023) Rust code
 - After building actors with `wash build`, we can inspect the resulting Wasm module with `wash inspect`
 - If we use `wasm-tools component wit` on the web assembly component that is built to see the imports and exports that are expected.
-- The host expects the interface that WASI provides here, so components that run on it must provie those.
+- The host expects the interface that WASI provides here, so components that run on it must provide those.
 - You can use the `just run-actor` in the repo to do some of the local things that are possible there (use `just` to see a list of available commands)
 
 #### Question: how does the code look like? (Kevin)
@@ -94,7 +94,7 @@ It's a custom function that's written but it's necessary to write the HTTP respo
 - The [Host Metrics RFC](https://github.com/wasmCloud/wasmCloud/issues/664) is a great example, thanks to Patrick for putting it up
   - The last time we commented on this was
 - While we have a process around RFCS to propose, accept & close -- we don't have an official process for moving something from proposed to accepted.
-- It would be a good idea for maintainers in the relevant project to vote on accepted RFCs to move them from proposed to acepted.
+- It would be a good idea for maintainers in the relevant project to vote on accepted RFCs to move them from proposed to accepted.
   - Once it's been accepted, we could push the RFC through to the roadmap.
 - What we're going to ask Patrick to do (like other RFC proposers) is to put a comment tagging relevant maintainers to ask for approval after a couple of rounds for discussion.
   - To somewhat formalize it we can specify something like "2 maintainers have to approve".

@@ -20,7 +20,7 @@ date: 2023-11-15
 - We have a bunch of new control interface topics/features that we'd like to discuss. We'd like to
   get some feedback on them before we merge them into main.
   - First up is the ability to adjust labels on actors. This is a feature that both allows for
-    scheduling (letting wadm make scheduing decisions) and for features like drain/cordon/lame duck
+    scheduling (letting wadm make scheduling decisions) and for features like drain/cordon/lame duck
     mode.
     - There is a possible security concern, but Kevin pointed out that other tech like Kubernetes
       doesn't have an answer to this either. There could be other edge cases

@@ -48,7 +48,7 @@ date: 2023-11-29
 - Jochan Rau: We implement a data processing actor - using messaging. In linkdef we need to give the creds. We could use key value store but it's more meta level and not really the responsibility of the actor to know where the creds are stored. Is there a way to make this easier and make sure our creds are protected?
   - Secrets management strategy has been discussed and there is a stale RFC for a basic level of secrets config.
   - Our answer right now is to use a providers like the Hashicorp Vault implementation in order to store secrets.
-  - The big question around that is if you need to send the secret over the wire. E.g. pull out Github secret to send over HTTP - will go over NATS in the current methodology and expose sensitive data.
+  - The big question around that is if you need to send the secret over the wire. E.g. pull out GitHub secret to send over HTTP - will go over NATS in the current methodology and expose sensitive data.
   - We'll bring up this RFC again - tokenization on the linkdef is important. More to come on this in the coming months.
   - Team to sync with Jochen in Slack.
 - There was plenty of additional discussion and plenty of insight from Victor, so check out the recording below.

@@ -43,7 +43,7 @@ date: 2024-02-21
 ### COMMUNITY DISCUSSION AND Q&A
 
 - Colin: Fuzzing (send random bits and see if it creates fatal errors).
-  - Fuzzing in rust unless you want to stand up the entire wasmCoud host every time, it's hard to call a specific function without standing everything up.
+  - Fuzzing in rust unless you want to stand up the entire wasmCloud host every time, it's hard to call a specific function without standing everything up.
   - Limitations of macros on top of macros.
   - Mock All - most commonly used.
   - Anyone have any familiarity mocking/fuzzing in Rust?