Requirements & Architecture
Supported Linux families, required privileges, storage locations and the shell-native architecture used by One-Click.
One-Click documentation · Step-by-step guide
Platforms
One-Click targets mainstream Linux distributions in the Debian and RHEL families. The public project documentation lists Debian, Ubuntu, CentOS, Fedora, Rocky Linux and AlmaLinux as supported families.
Privileges
Most control-plane operations modify system configuration and therefore require root. Read-only system information can bypass some of the heavier setup path, while firewall, package, virtualisation and recovery operations remain privileged.
Local State
/etc/one-clickConfiguration and persistent One-Click state./var/cache/one-clickCached module copies used by the loader./var/log/one-clickOperational and error logs./usr/local/bin/one-clickNormal command path after setup.Architecture Principles
- Shell-native control instead of an always-on web panel.
- Module loading only for operational capabilities that are invoked.
- SSH/Ansible controller-driven Fleet orchestration.
- Linux-native users, services and web-server isolation for hosted applications.
- Temporary web access for selected administration tasks instead of permanent management portals.