Feature Request: Support for Unattended/Non-Interactive Installation

[amiorin]

The Problem

I am currently attempting to automate the installation of ONCE using Ansible. However, the current shell script includes a run_once step (or similar interactive prompts) that requires manual intervention. This makes it difficult to include in CI/CD pipelines or configuration management scripts without maintaining a custom fork of the installer.

Suggested Solution

It would be helpful if the installation script supported flags or parameters to bypass interactive prompts, allowing for a fully unattended installation.

Following the pattern used by other popular installers (like Nix), we could pass arguments through the shell:

curl -fsSL https://once.com/install.sh | sh -s -- --unattended

Alternatives Considered

• Forking: I currently have to fork the install script to manually strip out the interactive components.

Additional Context

Enabling this would make ONCE much friendlier for DevOps workflows and automated server provisioning.

[kevinmcconnell]

@amiorin the only interactive prompts should be the sudo prompt. Does it help if you do your install as root, so that those are avoided? Or am I misunderstanding what you’re running into here?

[amiorin]

Apologies for the confusion. I should have been more specific. It's the TUI (Terminal User Interface) that requires manual interaction.

It would be great if the script supported a flag to skip the TUI entirely. Ideally, it would complete the installation and exit immediately after launching the background process: once background run --namespace once. This would allow the script to finish cleanly in a non-interactive CI/CD environment.

[kevinmcconnell]

Ah I see what you mean, yes. Sorry for the misunderstanding!

Yes I agree, a way to specify that you want the tool installed but not launched makes sense 👍 I'll take a look.