Feature Request - Method for Non-Interactive installation

[AntarktisZ11]

Is your feature request related to a problem? Please describe.

I setup my Klipper machines using Ansible automation but it is very close to being impossible to do this installation in a clean way.

Describe the solution you'd like

Running the installation with options already filled in, either via command-line, environment variables, or via the .env file, would result in a successful installation. If any options are missing or malformed, installation fails. Could trigger the non-interactive mode via an initial switch such as -noint.

Describe alternatives you've considered

I've tried using the expect executable, but it does not seem to work correctly in this instance. I may be using it wrong.

Additional information

No response

[github-actions]

Please use markdown syntax (``) for code snippets in your issue. You have confirmed the checkbox that you are using markdown, but none was recognized here. The markdown syntax makes your issue more readable and makes it easier to find a solution to your problem more quickly.

Examples:
The symbol turnscodeintocode`.

For more code use ` three times at the beginning and at the end like this:

some
code

turns into:

some
code

Please edit your outgoing post immediately. If you think that this hint is not necessary and you have correctly used markdown, then you can simply ignore this message.

[Tylerjet]

Hrmm It should be pretty straight forward to be able to create either an env or config where you would set all the options you want and provide that as a parameter with a path to that config.

Just not sure when that would get implement as I am still working on the installer rewrite/improvement but that has been on hold from work/life stuff.

[Tylerjet]

I've been thinking of making the installer more of a read only script as half the installer code right now is just user input and formatting those inputs. Where as a config with everything set before hand allows you to set once and use over again which is indeed much cleaner and easily automated. So this may become a part of that rewrite.