starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1592] [Feature Request] Multiple Servers with Multiple folders ( Using Symlink to save Space ) #1244

New issue

Open

opened 2026-02-27 02:56:05 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:56:05 +03:00

Owner

Originally created by @ghost on GitHub (Aug 25, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1592

It would be nice if something like this was available on LinuxGSM
Some files like .cfg files, .ini files, etc, should be unique...

It makes multiple server managing very easier..

Sorry for bad English

Originally created by @ghost on GitHub (Aug 25, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1592 It would be nice if something like this was available on LinuxGSM Some files like .cfg files, .ini files, etc, should be unique... It makes multiple server managing very easier.. Sorry for bad English

kerem added the

type: feature

label

2026-02-27 02:56:05 +03:00

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@naxIO commented on GitHub (Aug 26, 2017):

Would love to have that. I'm now running 10 different games with 10 different users but it would be much cooler if I could manage them all through. Also (optional) a neat webinterface for switching servers on/off would be awesome!

@naxIO commented on GitHub (Aug 26, 2017): Would love to have that. I'm now running 10 different games with 10 different users but it would be much cooler if I could manage them all through. Also (optional) a neat webinterface for switching servers on/off would be awesome!

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@UltimateByte commented on GitHub (Aug 27, 2017):

No need to symlink things when game servers allow you to use different config files.
https://github.com/GameServerManagers/LinuxGSM/wiki/Multiple-Game-Servers

@UltimateByte commented on GitHub (Aug 27, 2017): No need to symlink things when game servers allow you to use different config files. https://github.com/GameServerManagers/LinuxGSM/wiki/Multiple-Game-Servers

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@ghost commented on GitHub (Sep 7, 2017):

@UltimateByte That different config files is cool enough and I knew about them..
But in some point, Managing servers with different configs is hard, for example in CS:GO there is config files like "gamemode_casual.cfg", Sometimes a file like this affects the Main CFG, I set "mp_freezetime 0" for a server, and this file overwrites that, If I edit this file, then all the servers will be edited...

The same situation for server addons, We can have multiple Sourcemods and define them using "+sm_basepath addons/Server2" but the all of the forked sourcemods will use the same "csgo/cfg/sourcemod" directory

Sorry for bad English again, I hope u understand what I mean

@ghost commented on GitHub (Sep 7, 2017): @UltimateByte That different config files is cool enough and I knew about them.. But in some point, Managing servers with different configs is hard, for example in CS:GO there is config files like "gamemode_casual.cfg", Sometimes a file like this affects the Main CFG, I set "mp_freezetime 0" for a server, and this file overwrites that, If I edit this file, then all the servers will be edited... The same situation for server addons, We can have multiple Sourcemods and define them using "+sm_basepath addons/Server2" but the all of the forked sourcemods will use the same "csgo/cfg/sourcemod" directory Sorry for bad English again, I hope u understand what I mean

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@togenshi commented on GitHub (Oct 22, 2017):

I use layered overlayfs to get around this problem. Lowest Directory is a base LGSM install with minor tweaks then use an upper directory with the instance specific files.

The only issue is updating as all the instances need to be off at the same time. However you can get around this problem by using layered lower directories.

So when a new update comes in, the workflow is an follows:

Create another overlayfs mount over the base install.
Enter the new overlayfs mount and update the server and supporting mods.
Unmount the new overlayfs.
Stop the game instance when convenient, remount the overlayfs with the upperdir of the latest delta and base install.

I would go into more detail but got work soon. But this way allows easy backups (only need the upperdir files backed up) and conforms to best practices of many game servers. I was using ansible for this process.

@togenshi commented on GitHub (Oct 22, 2017): I use layered overlayfs to get around this problem. Lowest Directory is a base LGSM install with minor tweaks then use an upper directory with the instance specific files. The only issue is updating as all the instances need to be off at the same time. However you can get around this problem by using layered lower directories. So when a new update comes in, the workflow is an follows: 1. Create another overlayfs mount over the base install. 2. Enter the new overlayfs mount and update the server and supporting mods. 3. Unmount the new overlayfs. 4. Stop the game instance when convenient, remount the overlayfs with the upperdir of the latest delta and base install. I would go into more detail but got work soon. But this way allows easy backups (only need the upperdir files backed up) and conforms to best practices of many game servers. I was using ansible for this process.

kerem commented

2026-02-27 02:56:06 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jul 13, 2020):

overlayfs might be a good solution for managing and separating mods and configs

@dgibbs64 commented on GitHub (Jul 13, 2020): overlayfs might be a good solution for managing and separating mods and configs