Skip to content

Latest commit

 

History

History
61 lines (45 loc) · 3.7 KB

04-frontend.md

File metadata and controls

61 lines (45 loc) · 3.7 KB

Magic 8 Ball Frontend

Let's make our Magic 8 Ball application more interactive by adding a frontend where you can submit your question to the omniscient 8 ball! To do this, we want to add a new component to our Spin application that can serve the frontend of our application. Fortunately, Spin has a static file server component that can be added to any Spin application using spin add. Since this will be the base of our application, we must overwrite the default component trigger with the wildcard /... to match all routes.

We also need to tell the fileserver which frontend files to serve. Choose the default assets when asked for the 'Directory containing the files to serve'. In your Spin app's directory create a folder named assets.

For the purposes of this workshop, we've already prepared an HTML, CSS and JS frontend that you can reuse. Download these files into the assets folder.

$ spin add fileserver -t static-fileserver
HTTP path: /...
Directory containing the files to serve: assets

Let's take a look at the fileserver component that has now been added to the application manifest (spin.toml). In the component there is a files field. Since Wasm has a capability-based security model, a module can only access files that have been explicitly allowed by the Wasm runtime (wasmtime). This tells Spin to enable the module to read those files at runtime. We set the destination for the files to be the root directory as this is where the fileserver module is configured to look for them.

[[trigger.http]]
route = "/..."
component = "fileserver"

[component.fileserver]
source = { url = "https://github.com/fermyon/spin-fileserver/releases/download/v0.2.1/spin_static_fs.wasm", digest = "sha256:5f05b15f0f7cd353d390bc5ebffec7fe25c6a6d7a05b9366c86dcb1a346e9f0f" }
files = [{ source = "assets", destination = "/" }]

Let's look at the frontend implementation. The user asks a question and calls our Magic 8 Ball magic-8 component to get the response. This is done in the fetch('../magic-8') call in the JS portion of the snippet below. You can see that we are also passing the question in the body of the request. We will use this in a later step of the workshop. Don't worry about copying the code snippet below. This is just for illustrative purposes.

const btn = document.getElementById("btn");
btn.addEventListener("click", function () {
  var question = document.getElementById("question").value;
  fetch("../magic-8", { method: "POST", body: question })
    .then((response) => response.json())
    .then((data) => {
      document.getElementById("triangle").style.display = "inline-block";
      document.getElementById("circle").style.display = "inline-block";
      document.getElementById("triangle").innerHTML = "<br><br>" + data.answer;
    });
});

Now, we are ready to build and run our application. Run this command and click on the URL to see the Magic 8 Ball frontend.

spin build --up

Learning Summary

In this section you learned how to:

  • Add a new component to an existing Spin app using spin add
  • Use the Spin static fileserver component
  • Call one Spin component from another Spin component

Navigation