In all tutorials and quickstarts we specify --server local

Author: jdetter

docs/docs/03-Unity Tutorial/03-part-2.md

@@ -422,15 +422,15 @@ Created new database with name: blackholio, identity: c200d2c69b4524292b91822afa
 Next, use the `spacetime` command to call our newly defined `debug` reducer:
 
 ```sh
-spacetime call blackholio debug
+spacetime call --server local blackholio debug
 ```
 
 </TabItem>
 <TabItem value="csharp" label="C#">
 Next, use the `spacetime` command to call our newly defined `Debug` reducer:
 
 ```sh
-spacetime call blackholio Debug
+spacetime call --server local blackholio Debug
 ```
 
 </TabItem>
@@ -439,7 +439,7 @@ spacetime call blackholio Debug
 If the call completed successfully, that command will have no output, but we can see the debug logs by running:
 
 ```sh
-spacetime logs blackholio
+spacetime logs --server local blackholio
 ```
 
 You should see something like the following output:
@@ -472,7 +472,7 @@ The `client_connected` argument to the `spacetimedb::reducer` macro indicates to
 
 > SpacetimeDB gives you the ability to define custom reducers that automatically trigger when certain events occur.
 >
-> - `init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish <name> --delete-data`.
+> - `init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish --server local <name> --delete-data`.
 > - `client_connected` - Called when a user connects to the SpacetimeDB database. Their identity can be found in the `sender` value of the `ReducerContext`.
 > - `client_disconnected` - Called when a user disconnects from the SpacetimeDB database.
 
@@ -492,7 +492,7 @@ The `ReducerKind.ClientConnected` argument to the `SpacetimeDB.Reducer` attribut
 
 > SpacetimeDB gives you the ability to define custom reducers that automatically trigger when certain events occur.
 >
-> - `ReducerKind.Init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish <name> --delete-data`.
+> - `ReducerKind.Init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish --server local <name> --delete-data`.
 > - `ReducerKind.ClientConnected` - Called when a user connects to the SpacetimeDB database. Their identity can be found in the `Sender` value of the `ReducerContext`.
 > - `ReducerKind.ClientDisconnected` - Called when a user disconnects from the SpacetimeDB database.
 
@@ -690,7 +690,7 @@ Subscription applied indicates that the SpacetimeDB SDK has evaluated your subsc
 We can also see that the server has logged the connection as well.
 
 ```sh
-spacetime logs blackholio
+spacetime logs --server local blackholio
 ...
 2025-01-10T03:51:02.078700Z DEBUG: src/lib.rs:63: c200fb5be9524bfb8289c351516a1d9ea800f70a17a9a6937f11c0ed3854087d just connected.
 ```

docs/docs/03-Unity Tutorial/05-part-4.md

@@ -604,7 +604,7 @@ Notice that the food automatically respawns as you vaccuum them up. This is beca
 
 ## Connecting to Maincloud
 
-- Publish to Maincloud `spacetime publish -s maincloud <your database name> --delete-data`
+- Publish to Maincloud `spacetime publish --server maincloud <your database name> --delete-data`
   - `<your database name>` This name should be unique and cannot contain any special characters other than internal hyphens (`-`).
 - Update the URL in the Unity project to: `https://maincloud.spacetimedb.com`
 - Update the module name in the Unity project to `<your database name>`.
@@ -626,7 +626,7 @@ private void Start()
 }
 ```
 
-To delete your Maincloud database, you can run: `spacetime delete -s maincloud <your database name>`
+To delete your Maincloud database, you can run: `spacetime delete --server maincloud <your database name>`
 
 # Conclusion
 

docs/docs/04-Unreal Tutorial/03-part-2.md

@@ -409,15 +409,15 @@ Created new database with name: blackholio, identity: c200d2c69b4524292b91822afa
 <TabItem value="rust" label="Rust">
 
 ```sh
-spacetime call blackholio debug
+spacetime call --server local blackholio debug
 ```
 
 </TabItem>
 <TabItem value="csharp" label="C#">
 Next, use the `spacetime` command to call our newly defined `Debug` reducer:
 
 ```sh
-spacetime call blackholio Debug
+spacetime call --server local blackholio Debug
 ```
 
 </TabItem>
@@ -426,7 +426,7 @@ spacetime call blackholio Debug
 If the call completed successfully, that command will have no output, but we can see the debug logs by running:
 
 ```sh
-spacetime logs blackholio
+spacetime logs --server local blackholio
 ```
 
 You should see something like the following output:
@@ -459,7 +459,7 @@ The `client_connected` argument to the `spacetimedb::reducer` macro indicates to
 
 > SpacetimeDB gives you the ability to define custom reducers that automatically trigger when certain events occur.
 >
-> - `init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish <name> --delete-data`.
+> - `init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish --server local <name> --delete-data`.
 > - `client_connected` - Called when a user connects to the SpacetimeDB database. Their identity can be found in the `sender` value of the `ReducerContext`.
 > - `client_disconnected` - Called when a user disconnects from the SpacetimeDB database.
 
@@ -479,7 +479,7 @@ The `ReducerKind.ClientConnected` argument to the `SpacetimeDB.Reducer` attribut
 
 > SpacetimeDB gives you the ability to define custom reducers that automatically trigger when certain events occur.
 >
-> - `ReducerKind.Init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish <name> --delete-data`.
+> - `ReducerKind.Init` - Called the first time you publish your module and anytime you clear the database with `spacetime publish --server local <name> --delete-data`.
 > - `ReducerKind.ClientConnected` - Called when a user connects to the SpacetimeDB database. Their identity can be found in the `Sender` value of the `ReducerContext`.
 > - `ReducerKind.ClientDisconnected` - Called when a user disconnects from the SpacetimeDB database.
 
@@ -753,7 +753,7 @@ Subscription applied indicates that the SpacetimeDB SDK has evaluated your subsc
 We can also see that the server has logged the connection as well.
 
 ```sh
-spacetime logs blackholio
+spacetime logs --server local blackholio
 ...
 2025-01-10T03:51:02.078700Z DEBUG: src/lib.rs:63: c200fb5be9524bfb8289c351516a1d9ea800f70a17a9a6937f11c0ed3854087d just connected.
 ```

docs/docs/04-Unreal Tutorial/05-part-4.md

@@ -644,15 +644,15 @@ Notice that the food automatically respawns as you vaccuum them up. This is beca
 
 ## Connecting to Maincloud
 
-- Publish to Maincloud `spacetime publish -s maincloud <your database name> --delete-data`
+- Publish to Maincloud `spacetime publish --server maincloud <your database name> --delete-data`
   - `<your database name>` This name should be unique and cannot contain any special characters other than internal hyphens (`-`).
 - Update the URL in the Unreal project to: `https://maincloud.spacetimedb.com`
 - Update the module name in the Unreal project to `<your database name>`.
 - Your `BP_GameManager` should look something like this:
 
 ![Maincloud Setup](/images/unreal/part-4-01-maincloud.png)
 
-To delete your Maincloud database, you can run: `spacetime delete -s maincloud <your database name>`
+To delete your Maincloud database, you can run: `spacetime delete --server maincloud <your database name>`
 
 ## Conclusion
 

docs/docs/06-Server Module Languages/02-rust-quickstart.md

@@ -245,21 +245,21 @@ And that's all of our module code! We'll run `spacetime publish` to compile our
 From the `quickstart-chat` directory, run in another tab:
 
 ```bash
-spacetime publish --project-path spacetimedb quickstart-chat
+spacetime publish --server local --project-path spacetimedb quickstart-chat
 ```
 
 ## Call Reducers
 
 You can use the CLI (command line interface) to run reducers. The arguments to the reducer are passed in JSON format.
 
 ```bash
-spacetime call quickstart-chat send_message "Hello, World!"
+spacetime call --server local quickstart-chat send_message "Hello, World!"
 ```
 
 Once we've called our `send_message` reducer, we can check to make sure it ran by running the `logs` command.
 
 ```bash
-spacetime logs quickstart-chat
+spacetime logs --server local quickstart-chat
 ```
 
 You should now see the output that your module printed in the database.
@@ -276,7 +276,7 @@ You should now see the output that your module printed in the database.
 SpacetimeDB supports a subset of the SQL syntax so that you can easily query the data of your database. We can run a query using the `sql` command.
 
 ```bash
-spacetime sql quickstart-chat "SELECT * FROM message"
+spacetime sql --server local quickstart-chat "SELECT * FROM message"
 ```
 
 ```bash

docs/docs/06-Server Module Languages/04-csharp-quickstart.md

@@ -265,7 +265,7 @@ And that's all of our module code! We'll run `spacetime publish` to compile our
 From the `quickstart-chat` directory, run:
 
 ```bash
-spacetime publish --project-path spacetimedb quickstart-chat
+spacetime publish --server local --project-path spacetimedb quickstart-chat
 ```
 
 Note: If the WebAssembly optimizer `wasm-opt` is installed, `spacetime publish` will automatically optimize the Web Assembly output of the published module. Instruction for installing the `wasm-opt` binary can be found in [Rust's wasm-opt documentation](https://docs.rs/wasm-opt/latest/wasm_opt/).
@@ -275,13 +275,13 @@ Note: If the WebAssembly optimizer `wasm-opt` is installed, `spacetime publish`
 You can use the CLI (command line interface) to run reducers. The arguments to the reducer are passed in JSON format.
 
 ```bash
-spacetime call quickstart-chat SendMessage "Hello, World!"
+spacetime call --server local quickstart-chat SendMessage "Hello, World!"
 ```
 
 Once we've called our `SendMessage` reducer, we can check to make sure it ran by running the `logs` command.
 
 ```bash
-spacetime logs quickstart-chat
+spacetime logs --server local quickstart-chat
 ```
 
 You should now see the output that your module printed in the database.
@@ -295,7 +295,7 @@ info: Hello, World!
 SpacetimeDB supports a subset of the SQL syntax so that you can easily query the data of your database. We can run a query using the `sql` command.
 
 ```bash
-spacetime sql quickstart-chat "SELECT * FROM message"
+spacetime sql --server local quickstart-chat "SELECT * FROM message"
 ```
 
 ```bash

docs/docs/06-Server Module Languages/05-typescript-quickstart.md

@@ -38,13 +38,13 @@ Inside the `spacetimedb/` directory will be a `src/index.ts` entrypoint (require
 ## How to Build & Publish
 
 > [!IMPORTANT]
-> TypeScript modules are built and published with the `spacetime` CLI. `spacetime publish` will transpile and bundle your server module for you starting with the `src/index.ts` entrypoint. If you bundle your js yourself, you can specify `spacetime publish --js-path <path-to-your-bundle-file>` when publishing.
+> TypeScript modules are built and published with the `spacetime` CLI. `spacetime publish` will transpile and bundle your server module for you starting with the `src/index.ts` entrypoint. If you bundle your js yourself, you can specify `spacetime publish --server local --js-path <path-to-your-bundle-file>` when publishing.
 
 From the `spacetimedb/` directory you can lint/typecheck locally if you like, but to make the module live you’ll publish it to a database:
 
 ```bash
 cd spacetimedb
-spacetime publish --project-path spacetimedb quickstart-chat
+spacetime publish --server local --project-path spacetimedb quickstart-chat
 ```
 
 Publishing bundles your TypeScript into a single artifact and installs it into the `quickstart-chat` database.
@@ -203,7 +203,7 @@ spacetime start
 From the `quickstart-chat` directory (the parent of `spacetimedb/`):
 
 ```bash
-spacetime publish --project-path spacetimedb quickstart-chat
+spacetime publish --server local --project-path spacetimedb quickstart-chat
 ```
 
 You can choose any unique, URL-safe database name in place of `quickstart-chat`. The CLI will show the database **Identity** (a hex string) as well; you can use either the name or identity with CLI commands.
@@ -215,13 +215,13 @@ Use the CLI to call reducers. Arguments are passed as JSON (strings may be given
 Send a message:
 
 ```bash
-spacetime call quickstart-chat send_message "Hello, World!"
+spacetime call --server local quickstart-chat send_message "Hello, World!"
 ```
 
 Check that it ran by viewing logs (owner-only):
 
 ```bash
-spacetime logs quickstart-chat
+spacetime logs --server local quickstart-chat
 ```
 
 You should see output similar to:
@@ -238,7 +238,7 @@ You should see output similar to:
 SpacetimeDB supports a subset of SQL so you can query your data:
 
 ```bash
-spacetime sql quickstart-chat "SELECT * FROM message"
+spacetime sql --server local quickstart-chat "SELECT * FROM message"
 ```
 
 Output will resemble: