Muse
6a5ee8f77b
Display L-UI; panel binary/process l-ui, agent lui-agent. Dirs /usr/local/l-ui, /etc/l-ui, /var/log/l-ui; DB /etc/l-ui/l-ui.db (name file drives it via GetName), probe.db beside it, cert /etc/l-ui/cert, bin /usr/local/l-ui/bin. Services l-ui.service / lui-agent.service, OpenRC lui-agent, l-ui.sh, cmd/lui-agent. Env prefix XUI_ -> LUI_ (code reads new prefix only). Release assets l-ui-linux-* / lui-agent-linux-*; Gitea repo rogue/l-ui is a placeholder pending user confirmation (see selfupdate.go note). Go module path github.com/mhsanaei/3x-ui/v3 intentionally kept. Versions unchanged: panel V2.6.0 / agent A2.5.0.
L-UI on Hetzner Cloud
Hetzner Cloud does not have a third-party image marketplace the way AWS does.
Ship L-UI via cloud-init: each instance installs non-interactively and
generates unique per-instance credentials (no admin/admin, no shared secret).
cloud-init (no image build)
Use the generic user-data from ../../cloud-init/. It installs
L-UI non-interactively and generates unique per-instance credentials.
Web console: Create Server → Cloud config → paste
deploy/cloud-init/cloud-init.yaml.
CLI:
hcloud server create \
--name xui-1 \
--type cx22 \
--image ubuntu-24.04 \
--user-data-from-file deploy/cloud-init/cloud-init.yaml
After boot, fetch the generated credentials:
ssh root@<server-ip> 'cat /etc/l-ui/install-result.env'
"App"-style listing
Hetzner's curated apps live in the community repo
github.com/hetznercloud/apps: each app
is essentially a documented cloud-init config plus metadata. To propose L-UI as
a Hetzner app, follow that repo's contribution pattern and base the app's
cloud-config on deploy/cloud-init/cloud-init.yaml.