[GH-ISSUE #1376] Inputs as named variables #1066

New issue

Open

opened 2026-02-27 02:55:08 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:55:08 +03:00

Owner

Originally created by @jaredballou on GitHub (Mar 20, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1376

Hi all,

Something I started poking at with my LGSM branch was the inputs. I created a function to collect input which has four inputs. Prompt, variable_name, default, and options. It reads from environment variables and the script config to see if the user has already set the answer to a prompt, otherwise it displays the prompt and waits for input. If the script is on "unattended" mode, it uses default without stopping.

An option which is added is "A", which will save the choice to the script config file for the future. For example, running "console" I can answer "A" to the pre-console prompt so that it just goes right into console, and the same for if I run "console" and it needs to start the server.

The code is from a much older LGSM fork, I haven't finished merging the mainline updates to my branch, but if this sounds interesting I'll make a separate fork to put this in.

Originally created by @jaredballou on GitHub (Mar 20, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1376 Hi all, Something I started poking at with my LGSM branch was the inputs. I created a function to collect input which has four inputs. Prompt, variable_name, default, and options. It reads from environment variables and the script config to see if the user has already set the answer to a prompt, otherwise it displays the prompt and waits for input. If the script is on "unattended" mode, it uses default without stopping. An option which is added is "A", which will save the choice to the script config file for the future. For example, running "console" I can answer "A" to the pre-console prompt so that it just goes right into console, and the same for if I run "console" and it needs to start the server. The code is from a much older LGSM fork, I haven't finished merging the mainline updates to my branch, but if this sounds interesting I'll make a separate fork to put this in.

kerem added the

type: feature

info: docker

labels

2026-02-27 02:55:08 +03:00

kerem commented

2026-02-27 02:55:08 +03:00

Author

Owner

@UltimateByte commented on GitHub (Mar 20, 2017):

Hi @jaredballou :)

The way prompts work changed a lot.
You can have a look at the implementation here:
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/core_messages.sh#L272
and here for usage examples https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/command_fastdl.sh#L46-L63

I suggested to add an option to remove non-critical prompts (such as the one for console) with the use of a var here https://github.com/GameServerManagers/LinuxGSM/issues/1242

However, you gave me an idea : adding a config variable for each prompt so that users can select a default behavior.

configvar="ask/y/yes/n/no"

Thoughts ?

@UltimateByte commented on GitHub (Mar 20, 2017): Hi @jaredballou :) The way prompts work changed a lot. You can have a look at the implementation here: https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/core_messages.sh#L272 and here for usage examples https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/command_fastdl.sh#L46-L63 I suggested to add an option to remove non-critical prompts (such as the one for console) with the use of a var here https://github.com/GameServerManagers/LinuxGSM/issues/1242 However, you gave me an idea : adding a config variable for each prompt so that users can select a default behavior. ``` configvar="ask/y/yes/n/no" ``` Thoughts ?

kerem commented

2026-02-27 02:55:08 +03:00

Author

Owner

@jaredballou commented on GitHub (Mar 21, 2017):

That's sort of how I had it done, except with a bit more functionality. But that aside, the real use case I was building for was for Docker, so that the scripts could be run non-interactively. How do you let LGSM know that it should suppress most/all prompts right now?

@jaredballou commented on GitHub (Mar 21, 2017): That's sort of how I had it done, except with a bit more functionality. But that aside, the real use case I was building for was for Docker, so that the scripts could be run non-interactively. How do you let LGSM know that it should suppress most/all prompts right now?

kerem commented

2026-02-27 02:55:08 +03:00

Author

Owner

@UltimateByte commented on GitHub (Mar 21, 2017):

Not sure how yet, but you could tweak fn_prompt_yn so that it uses the ${initial} value without prompting.
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/core_messages.sh#L273-L293

@UltimateByte commented on GitHub (Mar 21, 2017): Not sure how yet, but you could tweak fn_prompt_yn so that it uses the ${initial} value without prompting. https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/core_messages.sh#L273-L293