You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: commands/fastdl.md
+16-18
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# fastdl
2
2
3
-
FastDL \(Fast Download\) allows the client to download custom server content \(maps, materials, models, particles, sounds, fonts, images\) from a web server.
3
+
FastDL (Fast Download) allows the client to download custom server content (maps, materials, models, particles, sounds, fonts, images) from a web server.
4
4
5
-
It is used to offload content downloads to a web server instead of relying on source servers \(SRCDS\) that only allows 20KBps downloads to clients. Content on the web server can be compressed to further speed up the download process. This means that custom content downloads much faster.
5
+
It is used to offload content downloads to a web server instead of relying on source servers (SRCDS) that only allows 20KBps downloads to clients. Content on the web server can be compressed to further speed up the download process. This means that custom content downloads much faster.
6
6
7
7
Valve now use steam workshop for most custom content however FastDL is still required in some cases.
8
8
@@ -20,20 +20,19 @@ Short: `./gameserver fd`
20
20
21
21
## Supported file formats
22
22
23
-
* Maps \(.bsp\)
24
-
* Materials \(.vtf, .vmt, .png, .svg\)
25
-
* Models \(.vtx, .vvd, .mdl, .phy\)
26
-
* Particles \(.pcf\)
27
-
* Sounds \(.wav, .mp3, .ogg\)
28
-
* Fonts \(.otf, .ttf\)
29
-
* Images \(.png, .svg\)
23
+
* Maps (.bsp)
24
+
* Materials (.vtf, .vmt, .png, .svg)
25
+
* Models (.vtx, .vvd, .mdl, .phy)
26
+
* Particles (.pcf)
27
+
* Sounds (.wav, .mp3, .ogg)
28
+
* Fonts (.otf, .ttf)
29
+
* Images (.png, .svg)
30
30
31
31
## Requirements
32
32
33
-
* Web server on the game server \(Apache/Nginx\).
34
-
35
-
or
33
+
* Web server on the game server (Apache/Nginx).
36
34
35
+
or
37
36
* Access to a remote web server.
38
37
39
38
## Usage
@@ -44,11 +43,11 @@ Run the FastDL command on your main LinuxGSM script. This will create a new dire
44
43
45
44
`./gameserver fastdl`
46
45
47
-
### Create A virtual Host \(local Apache web server\)
46
+
### Create A virtual Host (local Apache web server)
48
47
49
48
If Apache2 is being used a virtual host pointing to the newly created `public_html` directory can be used.
50
49
51
-
Tip: Apache2 mod "userdir" is useful if the Linux server is hosting [multiple game servers](../features/multiple-game-servers.md), as it creates a url for the current user `http://yourwebsite.ltd/~username`.
50
+
Tip: Apache2 mod "userdir" is useful if the Linux server is hosting [multiple game servers](../configuration/multiple-game-servers.md), as it creates a url for the current user `http://yourwebsite.ltd/~username`.
52
51
53
52
#### Tutorial on setup of Apache2 server with Virtual Hosts
54
53
@@ -62,7 +61,7 @@ Firstly make sure your subdomain redirects to your game server and that Apache2
62
61
63
62
See the example below and edit the relevent details.
@@ -115,4 +114,3 @@ Custom server content can be compressed using bzip2 which is supported by source
115
114
#### Garry's Mod Download enforcer
116
115
117
116
In order for a client to download files from a FastDL in Garry's Mod, the developer of an addon must put files from the addon into lua code `resource.Addfile ( "/path/to/file.ext" )`. However, some addon developers do not do this. In order for clients to download the required files, an lua file needs to be generated for it to work, which is what the lua enforcer feature does. The only downside is that clients may download files that are not required on the server.
This configuration file is automatically downloaded upon server installation.
43
43
44
44
## Config file naming
45
45
46
-
Whenever possible, LinuxGSM uses a custom name for configuration files that contains the `${servicename}` variable in it in order to allow the running of [multiple game servers](../features/multiple-game-servers.md) with different config files. If the game does not allow for that, then the usual name will be used.
46
+
Whenever possible, LinuxGSM uses a custom name for configuration files that contains the `${servicename}` variable in it in order to allow the running of [multiple game servers](multiple-game-servers.md) with different config files. If the game does not allow for that, then the usual name will be used.
47
47
48
48
### Example
49
49
50
50
For source servers, the default `server.cfg` is not used with LinuxGSM. Instead if you're running `./csgoserver`, then the config file will be called `csgoserver.cfg`.
51
51
52
52
## Missing configuration file handling
53
53
54
-
LinuxGSM will always check a config file is present when starting a server.
54
+
LinuxGSM will always check a config file is present when starting a server.\
55
55
If a config file is missing, it will re-download the default one or give a warning.
56
56
57
57
## Where are the settings I'm looking for?
@@ -64,5 +64,4 @@ One of the goals of LinuxGSM is to make managing these as easy as possible, by p
64
64
65
65
If you found settings that are absent from the default configuration file provided by LinuxGSM that would be a useful addition, then you can open an issue or a pull request.
Copy file name to clipboardexpand all lines: configuration/multiple-game-servers.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,15 @@
2
2
description: Hosting multiple game servers on the same host
3
3
---
4
4
5
-
# Multiple Game Servers
5
+
# Running Multiple Game Servers
6
6
7
7
Depending upon the game server you are running it is possible to run multiple game servers on the same server host.
8
8
9
9
**There are two recommended ways to run multiple game servers on one physical server**.\
10
10
Depending upon the circumstances you may choose a particular method or mixture of both.
11
11
12
12
It is best to make a proper plan for running multiple game servers at the earliest stage of your deployment.\
13
-
Make sure that you examined this page carefully and understood all of its content before starting.
13
+
Make sure that you examine this page carefully and understand all of its content before starting.
14
14
15
15
## Prerequisites
16
16
@@ -24,7 +24,7 @@ You need some definitions to make this guide clear.
24
24
/home/gameserver/serverfiles
25
25
```
26
26
27
-
***Instance:** Each individual game server is referred too as an _instance._ There might be multiple instances running per installation. An instance is started by running the `./gameserver` script
27
+
***Instance:** Each individual game server is referred to as an _instance._ There might be multiple instances running per installation. An instance is started by running the `./gameserver` script
28
28
29
29
```
30
30
/home/gameserver/gameserver
@@ -35,21 +35,21 @@ You need some definitions to make this guide clear.
35
35
36
36
#### LinuxGSM Configuration
37
37
38
-
You should be familiar with how [LinuxGSM Configs](../configuration/linuxgsm-config.md) work.
38
+
You should be familiar with how [LinuxGSM Configs](linuxgsm-config.md) work.
39
39
40
40
#### Understand ports
41
41
42
-
You need to understand how ports work in order to avoid port overlapping, otherwise your new instances won't start. Useful resource: [Ports](../networking/ports.md).
42
+
You need to understand how ports work in order to avoid port overlapping, otherwise, your new instances won't start. Useful resource: [Ports](../networking/ports.md).
43
43
44
44
## Single Instance per Installation
45
45
46
46
Single instance per installation is the most simple method and will fit most use cases. It keeps the server files and configs completely separate from each other.
47
47
48
-
This consists of creating a new user for each game server, repeat the install process and edit your config files ensuring default ports are changed.
48
+
This consists of creating a new user for each game server, repeating the install process, and edit your config files ensuring default ports are changed.
49
49
50
50
### Use cases
51
51
52
-
* Running different game servers require installation in a different directory
52
+
* Running different game servers requires installation in a different directory
53
53
* Running multiple servers of the same game, but they have different content, addons or mods.
54
54
* You want your game servers to be totally separate for simplicity and reduce the chance of multiple instances breaking all at once.
Copy file name to clipboardexpand all lines: game-servers/ark-survival-evolved.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -154,11 +154,11 @@ A cluster allows an admin to group ARK servers together, usually servers on diff
154
154
155
155
### Multi-Instance
156
156
157
-
ARK will not work with LinuxGSM [multi instances ](../features/multiple-game-servers.md)in the same directory. This is due to its reliance on `GameUserSettings.ini` meaning multiple instances must use the same settings.
157
+
ARK will not work with LinuxGSM [multi instances ](../configuration/multiple-game-servers.md)in the same directory. This is due to its reliance on `GameUserSettings.ini` meaning multiple instances must use the same settings.
158
158
159
159
### Adding Servers to Clusters
160
160
161
-
Firstly, setup [multiple ARK game server instances](../features/multiple-game-servers.md).
161
+
Firstly, setup [multiple ARK game server instances](../configuration/multiple-game-servers.md).
162
162
163
163
Change the command-line parameters for your server instances by editing the instance configs:
* Headless Client is used to offload AI calculations from the server.
16
-
* Headless Client is integrated into game client and dedicated server executable \(Windows and Linux, use -client parameter\).
16
+
* Headless Client is integrated into game client and dedicated server executable (Windows and Linux, use -client parameter).
17
17
* The server does not allow arbitrary connections from headless clients if you do not define the headless clients IPs in the server.cfg.
18
18
19
19
### Headless Client Setup and Usage
@@ -24,32 +24,32 @@ Starting up a headless client and having it connect to your server is easy, Crea
24
24
This guide only handles the setup and connecting a headless client.
25
25
{% endhint %}
26
26
27
-
Create a [new server instance](../features/multiple-game-servers.md) using LinuxGSM `./linuxgsm.sh arma3server`. This will become the headless client instance and rename the new instance to `arma3server-hc`.
27
+
Create a [new server instance](../configuration/multiple-game-servers.md) using LinuxGSM `./linuxgsm.sh arma3server`. This will become the headless client instance and rename the new instance to `arma3server-hc`.
28
28
29
29
Edit the config file `lgsm/config-lgsm/arma3server-hc.cfg`.
30
30
31
31
Change the `port=` increasing the number by a factor of 12 e.g 2303 becomes 2314.
32
32
33
33
Update `startparameters=` changing it to the following.
Edit the game server config of `arma3server`\(not the headless client\)`arma3server.server.cfg` and add the headless client IP address to `headlessClients[]=`. If the headless client is on the same physical server as the ARMA 3 server then also add the IP to `localClient[]=`.
39
+
Edit the game server config of `arma3server` (not the headless client) `arma3server.server.cfg` and add the headless client IP address to `headlessClients[]=`. If the headless client is on the same physical server as the ARMA 3 server then also add the IP to `localClient[]=`.
40
40
41
41
{% hint style="warning" %}
42
42
Do not use 127.0.0.1 as the IP address.
43
43
{% endhint %}
44
44
45
-
```text
45
+
```
46
46
headlessClients[]={"1.2.3.4"};
47
47
localClient[]={"1.2.3.4"};
48
48
```
49
49
50
50
Navigate to your profile directory.
51
51
52
-
```text
52
+
```
53
53
~cd ~/.local/share/Arma\ 3\ -\ Other\ Profiles
54
54
```
55
55
@@ -61,8 +61,6 @@ Start your headless client with `./arma3server-hc start`.
61
61
62
62
Only an admin can see the headless clients in the player menu on the server. The headless client will connect and automatically assume the first available headless client slot.
63
63
64
-
{% file src="../.gitbook/assets/a3\_hc\_tutorial.pdf" caption="In depth guide to headless clients" %}
65
-
66
64
## Mod Support
67
65
68
66
Arma 3 mods are managed using the [Steam Workshop](https://steamcommunity.com/app/346110/workshop/) or manual downloads.
@@ -83,7 +81,7 @@ Download the Mod using [https://steamworkshopdownloader.io/](https://steamworksh
83
81
84
82
Create a directory called `@cba_a3` in `serverfiles/mods`
85
83
86
-
```text
84
+
```
87
85
serverfiles/mods/@cba_a3
88
86
```
89
87
@@ -95,19 +93,19 @@ Remember to check you have the correct user permissions once uploaded
95
93
96
94
Copy the contents of the `@cba_a3/keys` directory to the server keys directory.
Add @cba\_a3 to the `mods=""` setting in the [LinuxGSM config](../configuration/linuxgsm-config.md).
103
101
104
-
```text
102
+
```
105
103
mods="mods/@cba_a3"
106
104
```
107
105
108
106
If you are adding multiple mods make sure you put a semicolon with the escape character in between each mod.
109
107
110
-
```text
108
+
```
111
109
mods="mods/@mod1\;mods/@mod2"
112
110
```
113
111
@@ -139,10 +137,10 @@ do
139
137
done
140
138
```
141
139
142
-
Start the server and check that your mods all have valid hashes.
140
+
Start the server and check that your mods all have valid hashes.\
143
141
You should see the "Community Base Addons" mod appear in your `console`[log](../features/logging.md)file.
144
142
145
-
```text
143
+
```
146
144
15:27:37 ============================================================================================= List of mods ===============================================================================================
147
145
15:27:37 modsReadOnly = true
148
146
15:27:37 safeModsActivated = false
@@ -167,4 +165,3 @@ You should see the "Community Base Addons" mod appear in your `console` [log](..
167
165
15:27:37 Arma 3 | A3 | true | true | NOT FOUND | | |
Copy file name to clipboardexpand all lines: guides/security.md
+2-3
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ TO-DO
8
8
needs to be verified
9
9
{% endhint %}
10
10
11
-
\(NOTE: This method is detailed further [here](https://linux-audit.com/linux-system-hardening-adding-hidepid-to-proc/). The web page also describes how to give certain users the default full access to listing all processes.\)
11
+
(NOTE: This method is detailed further [here](https://linux-audit.com/linux-system-hardening-adding-hidepid-to-proc/). The web page also describes how to give certain users the default full access to listing all processes.)
12
12
13
13
By default, a user can see all started processes from other users, which is bad, but also their start parameters, which is pretty dangerous. Those start parameters can contain sensitive information, such as RCON password, Steam API keys and GSLT upon start, a Rust dedicated server is checking if the process name started by any user, and will prevent you from running it again if it finds it, displaying "Player is already running".
14
14
@@ -26,5 +26,4 @@ nano /etc/fstab
26
26
proc /proc proc defaults,hidepid=2 0 0
27
27
```
28
28
29
-
You still need to make one user per server, change ports, and repeat the install process. \(See [this](../features/multiple-game-servers.md) for more info\)
30
-
29
+
You still need to make one user per server, change ports, and repeat the install process. (See [this](../configuration/multiple-game-servers.md) for more info)
0 commit comments