Basic launcher setup page, add .NET SDK to tool installation list

Author: Heliodex

Docs/src/content/docs/guides/devsetup.mdoc

@@ -34,7 +34,7 @@ If you wish to use containers instead of SurrealDB and Go, install the latest ve
 	cd MercuryCore
 	```
 
- - If not using Git, you can also [download the repository as a compressed archive file](https://github.com/tp-link-extender/MercuryCore/archive/refs/heads/main.zip) (.zip) from the GitHub page and extract it to a directory of your choice.
+   - If not using Git, you can also [download the repository as a compressed archive file](https://github.com/tp-link-extender/MercuryCore/archive/refs/heads/main.zip) (.zip) from the GitHub page and extract it to a directory of your choice.
 
 2. If not using containers, navigate to the **Economy** directory, and run `go build` to compile the Economy service.
 

Docs/src/content/docs/guides/launchersetup.md

@@ -0,0 +1,63 @@
+---
+title: Launcher setup
+description: How to set up the Launcher, the application responsible for starting and handling Client sessions, for local development and production hosting.
+---
+
+
+This guide details how to set up the Mercury Launcher for local development, moderation, and production publishing. More information on the Launcher is available on the [Launcher service page](/services/launcher).
+
+## Requirements
+
+You will need:
+
+- Latest version of [Git](https://git-scm.com) installed (expected as `git`, optional)
+- Latest version of [.NET](https://dotnet.microsoft.com) installed (expected as `dotnet`)
+- A terminal
+
+## Instructions
+
+{% steps %}
+
+1. Clone the [tp-link-extender/MercuryLauncher](https://github.com/tp-link-extender/MercuryLauncher) repository to a directory of your choice on your local machine, and navigate to the root directory of the repository.
+
+	```bash
+	git clone https://github.com/tp-link-extender/MercuryLauncher
+	cd MercuryLauncher
+	```
+
+   - If not using Git, you can also [download the repository as a compressed archive file](https://github.com/tp-link-extender/MercuryLauncher/archive/refs/heads/main.zip) (.zip) from the GitHub page and extract it to a directory of your choice.
+
+2. Navigate to the **Config.fs** file and modify the configuration options as desired. See the [Launcher service page](/services/launcher#configuration) for more information on the available configuration options.
+
+3. Run `dotnet run` to test the Launcher. If everything is set up correctly, the Launcher will start building. Once it is complete, it will start, immediately attempting to install the latest Setup deployment from the configured URL. It will not attempt to start the Client or Studio.
+
+   - If this command is being run for the first time, a welcome message similar to the following will be printed to the console:
+
+		```
+		Welcome to .NET 10.0!
+		---------------------
+		SDK Version: 10.0.200
+
+		Telemetry
+		Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry
+
+		----------------
+		Installed an ASP.NET Core HTTPS development certificate.
+		To trust the certificate, run 'dotnet dev-certs https --trust'
+		Learn about HTTPS: https://aka.ms/dotnet-https
+
+		----------------
+		Write your first app: https://aka.ms/dotnet-hello-world
+		Find out what's new: https://aka.ms/dotnet-whats-new
+		Explore documentation: https://aka.ms/dotnet-docs
+		Report issues and find source on GitHub: https://github.com/dotnet/core
+		Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli
+		--------------------------------------------------------------------------------------
+		```
+
+4. After you have modified the source code as required and are ready to publish the launcher, run the corresponding command for the operating system you wish to publish for:
+
+	- Windows: `dotnet publish --nologo -o ./out -r win-x64`
+	- Linux: `dotnet publish --nologo -o ./out -r linux-x64`
+
+	These commands will each place the published executable in the **out** directory.

Docs/src/content/docs/install/index.md

@@ -5,7 +5,6 @@ description: Tools needed to use and develop Mercury Core, and how to install th
 
 This page describes how to install and manage the tools for development and production environments for Mercury Core.
 
-
 In the near future, we may provide a program for setting up and installing the necessary tools automatically. Please let us know if you would find that helpful.
 
 ## Baseline tools
@@ -35,10 +34,16 @@ For running without containers, install the following tools directly.
 To set up a development environment, install all tools from the [Baseline tools](#baseline-tools) section, as well as the following.
 
 - [Go](/install/go)
-	- It's possible to use the container instead if developing the Economy service, though this will be slower to start than compiling and running it directly with Go.
+ 	- It's possible to use the container instead if developing the Economy service, though this will be slower to start than compiling and running it directly with Go.
 
 ## Production tools
 
 To set up a production environment, install all tools from the [Baseline tools](#baseline-tools) section, as well as the following.
 
 - [Caddy](/install/caddy)
+
+## Other tools
+
+These are the tools needed to set up other parts of the Mercury Suite. They are not required for running Mercury Core.
+
+- .NET SDK, used to build the [Launcher](/services/launcher)

Docs/src/content/docs/services/launcher.md

@@ -4,6 +4,7 @@ description: Information about the Lanucher, the application responsible for sta
 ---
 
 This page provides information about the Mercury Launcher, responsible for downloading, installing, and unpacking Setup deployment packages. It also registers itself with the operating system to handle file associations, and should open when any place is joined from the Site, then launching the Client. An implementation of the Launcher is available at the [tp-link-extender/MercuryLauncher](https://github.com/tp-link-extender/MercuryLauncher) repository.
+
 With the modularity of the Mercury Suite, it is not required to use this implementation of the Launcher alongside Mercury Core, and a custom implementation or other launcher can be used instead. However, the custom Setup deployment format is designed to be used with the Launcher, and isn't compatible with the 'standard' deployment format. 
 
 ## Configuration
@@ -12,6 +13,6 @@ The Launcher can be configured by modifying the [**Config.fs**](https://github.c
 
 ## Building
 
-See the [Launcher setup](/guides/launchersetup) (todo) page for instructions on building the Launcher.
+See the [Launcher setup](/guides/launchersetup) page for instructions on building the Launcher.
 
 Any executables published by the building process are ~21MB in size and do not require any existing installation of the .NET SDK or runtime to run, as they are self-contained. These production builds do not contain any debug symbols. Build configuration can be modified by editing the [**MercuryLauncher.fsproj**](https://github.com/tp-link-extender/MercuryLauncher/blob/main/MercuryLauncher.fsproj) file.