Skip to content

Commit 880d0b9

Browse files
committed
Launcher configuration and building instructions details, more information about the Launcher
1 parent 1465814 commit 880d0b9

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

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

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,14 @@ description: Information about the Lanucher, the application responsible for sta
44
---
55

66
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.
7+
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.
78

89
## Configuration
910

10-
todo
11+
The Launcher can be configured by modifying the [**Config.fs**](https://github.com/tp-link-extender/MercuryLauncher/blob/main/Config.fs) file in the root of the repository. This includes options for the name of the Launcher, the domain name used for loading Setup packages and provided to the Client for communication with the Site, and the icon shown in the Launcher UI. Once this file is updated, the Launcher will need to be recompiled or republished for the changes to take effect.
12+
13+
## Building
14+
15+
See the [Launcher setup](/guides/launchersetup) (todo) page for instructions on building the Launcher.
16+
17+
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.

0 commit comments

Comments
 (0)