Updated setup section in the tutorial

Author: pvetere

docs/book.toml

@@ -3,7 +3,7 @@ authors = ["Bailey Hayes", "Peter Vetere", "Kyle Brown"]
 language = "en"
 multilingual = false
 src = "src"
-title = "SingleStore Wasm Toolkit"
+title = "SingleStore Wasm Tutorial"
 
 [output.html]
 

docs/src/SUMMARY.md

@@ -2,10 +2,6 @@
 
 - [Overview](Tutorial-Overview.md)
 - [Setup](Tutorial-Setup.md)
-	- [With a Development Container](Tutorial-Setup-Container.md)
-		- [VS Code Container](Tutorial-Setup-Container-VSCode.md)
-		- [Standalone Container](Tutorial-Setup-Container-Standalone.md)
-	- [Locally](Tutorial-Setup-Local.md)
 - [Examples](Tutorial-Examples.md)
 - [Writing WIT IDL](Tutorial-WIT.md)
 	- [WIT for the `power-of` Example](Tutorial-WIT-Power.md)

docs/src/Tutorial-Deploy-Power.md

@@ -1,7 +1,7 @@
 <!-- GENERATED FILE; DO NOT CHANGE! -->
 
 # Deploying the `power-of` Example
-Now that you've compiled and tested your Wasm function, it is ready for deployment into the database.  This can be done in multiple ways.  The easiest is probably to use the `pushwasm` tool, included in the `wasm-toolkit` development containers.  Alternatively, you can "pull" the Wasm module into the database by first uploading it to cloud storage (SingleStoreDB supports pulling Wasm modules from multiple cloud providers -- GCS, Azure, and S3).  We'll discuss both techniques.
+Now that you've compiled and tested your Wasm function, it is ready for deployment into the database.  This can be done in multiple ways.  One way is to use the `pushwasm` tool, provided in the development container.  Alternatively, you can "pull" the Wasm module into the database by first uploading it to cloud storage (SingleStoreDB supports pulling Wasm modules from multiple cloud providers -- GCS, Azure, and S3).  We'll discuss both techniques.
 
 Before we start, ensure that a destination database is available.  To do this, using your favorite SQL client, create a new database called `wasm_tutorial`.  For example, you might use the following statements:
 

docs/src/Tutorial-Deploy-Prologue.md

@@ -1,4 +1,4 @@
-Now that you've compiled and tested your Wasm function, it is ready for deployment into the database.  This can be done in multiple ways.  The easiest is probably to use the `pushwasm` tool, included in the `wasm-toolkit` development containers.  Alternatively, you can "pull" the Wasm module into the database by first uploading it to cloud storage (SingleStoreDB supports pulling Wasm modules from multiple cloud providers -- GCS, Azure, and S3).  We'll discuss both techniques.
+Now that you've compiled and tested your Wasm function, it is ready for deployment into the database.  This can be done in multiple ways.  One way is to use the `pushwasm` tool, provided in the development container.  Alternatively, you can "pull" the Wasm module into the database by first uploading it to cloud storage (SingleStoreDB supports pulling Wasm modules from multiple cloud providers -- GCS, Azure, and S3).  We'll discuss both techniques.
 
 Before we start, ensure that a destination database is available.  To do this, using your favorite SQL client, create a new database called `wasm_tutorial`.  For example, you might use the following statements:
 

docs/src/Tutorial-Deploy-Split.md

@@ -1,7 +1,7 @@
 <!-- GENERATED FILE; DO NOT CHANGE! -->
 
 # Deploying the `split-str` Example
-Now that you've compiled and tested your Wasm function, it is ready for deployment into the database.  This can be done in multiple ways.  The easiest is probably to use the `pushwasm` tool, included in the `wasm-toolkit` development containers.  Alternatively, you can "pull" the Wasm module into the database by first uploading it to cloud storage (SingleStoreDB supports pulling Wasm modules from multiple cloud providers -- GCS, Azure, and S3).  We'll discuss both techniques.
+Now that you've compiled and tested your Wasm function, it is ready for deployment into the database.  This can be done in multiple ways.  One way is to use the `pushwasm` tool, provided in the development container.  Alternatively, you can "pull" the Wasm module into the database by first uploading it to cloud storage (SingleStoreDB supports pulling Wasm modules from multiple cloud providers -- GCS, Azure, and S3).  We'll discuss both techniques.
 
 Before we start, ensure that a destination database is available.  To do this, using your favorite SQL client, create a new database called `wasm_tutorial`.  For example, you might use the following statements:
 

docs/src/Tutorial-Setup-Container-Standalone.md

@@ -2,8 +2,16 @@
 
 For each example in this tutorial, it will be useful to create yourself a separate work directory in which to put your code and compiled artifacts. This will help keep your files for each example organized.
 
-In addition to a SQL client and SingleStore database, you’ll need a few other things to get your environment set up properly. For this, you have some options:
+In addition to a SQL client and SingleStore database, you'll need Docker or some other container runtime.  SingleStore's recommended workflow uses a special development container to ensure that you have all the dependencies needed to build a Wasm UDF or UDAF.  To help with this, we've created a handy [wrapper script](https://github.com/singlestore-labs/singlestore-wasm-toolkit/blob/main/scripts/dev-shell) that will start the shell.  You can download the script directly [here](https://raw.githubusercontent.com/singlestore-labs/singlestore-wasm-toolkit/refs/heads/main/scripts/dev-shell).
 
-- Use a [development container](Tutorial-Setup-Container.md) (recommended)
-- Install development dependencies [locally](Tutorial-Setup-Local.md)
+Once you've downloaded the script, ensure that it has executable permissions and is in your `PATH`.  Then, open a command prompt and run the following command.  The argument is the path to the intended root of your Wasm module's source code (it must exist first).  For example: `dev-shell /home/$USER/src/my-wasm-project`.
+
+When the shell starts, you should see the following prompt:
+```
+[dev-shell]:~/src %
+```
+
+The `src` directory will have been mounted from path you passed to the `dev-shell` script.  It is *not* necessary to write the code for this tutorial inside the container's shell; you may use your preferred editing workflow for this.  However, please *do* be sure to run all suggested build and deployment commands inside the container's shell so that you have access to the necessary tools.
+
+Next, let's pick an [example](Tutorial-Examples.md) to work through.