From 1722728ef3a53124c81fe8134c05af6abe4d6bed Mon Sep 17 00:00:00 2001 From: Cyberboss Date: Sat, 21 Oct 2017 21:36:57 -0400 Subject: [PATCH] Update the readme --- README.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index da95fa5e57..f301c43ea2 100644 --- a/README.md +++ b/README.md @@ -73,7 +73,7 @@ This process is identical to the above steps in command line mode. You can alway 1. Obtain an SSL certificate to secure the connection (this is beyond the scope of this guide) 1. Either stick with the default port `38607` or change it with `admin set-port ` -1. [Bind the SSL certificate to port 38607](https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-configure-a-port-with-an-ssl-certificate) +1. [Bind the SSL certificate to the port](https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-configure-a-port-with-an-ssl-certificate) - e.g. `netsh http add sslcert ipport=0.0.0.0: certhash= appid={F32EDA25-0855-411C-AF5E-F0D042917E2D}` - The `appid` GUID actually doesn't matter, but for sanity, you should use the GUID of TGServerService.exe as printed above 1. Ensure the port can be acccessed from the internet @@ -97,6 +97,9 @@ The service supports updates while running a DreamDaemon instance. Simply instal * This is a symbolic link pointing to current "live" folder. * When the server is updated, we just point this to the updating folder so that the update takes place next round. +* `Diagnostics` + * This contains various timestamped diagnostic information for DreamDaemon invocations + * `Repository/` * This contains the actual git repository, all changes in here will be overwritten during update operations. @@ -118,6 +121,9 @@ The service supports updates while running a DreamDaemon instance. Simply instal * `prtestjob.json` * This contains information about current test merged pull requests in the Repository folder +* `TGS3.json` + * This is a copy of TGS3.json from the Repository. If a repostory change creates differences between the two, update operations will be blocked until the user confirms they want to change it + ### Starting the game server: To run the game server, open the `Server` tab of the control panel and click either `Start` @@ -168,7 +174,7 @@ You can clear all active test merges using `Reset to Origin Branch` in the `Repo ### Viewing Server Logs * Logs are stored in the Windows event viewer under `Windows Logs` -> `Application`. You'll need to filter this list for `TG Station Server` -* Every event type is keyed with an ID. A complete listing of these IDs can be found [here](https://github.com/tgstation/tgstation-server/blob/master/TGServerService/ServerService.cs#L15). +* Every event type is keyed with an ID. A complete listing of these IDs and their purpose can be found [here](https://github.com/tgstation/tgstation-server/blob/master/TGServerService/EventID.cs). * You can also import the custom view `View TGS3 Logs.xml` in this folder to have them automatically filtered ### Enabling upstream changelog generation @@ -180,7 +186,7 @@ You can clear all active test merges using `Reset to Origin Branch` in the `Repo ## CONTRIBUTING -* Version numbers and releases will be handled by maintainers, do not modify these in your PR +* See [CONTRIBUTING.md](https://github.com/tgstation/tgstation-server/.github/CONTRIBUTING.md) ## LICENSING