See the container list
Review container names, running state, addresses, resource information, and available actions in one view.
Replace repetitive terminal steps with a focused interface.
When your operators repeatedly reconstruct commands, look up identifiers, check status, and wait for results, FoleyBridge can put those actions into a tool built for the environment. LXTUI demonstrates the idea with a keyboard-driven terminal interface for LXC and LXD containers.
Inspect the public source
The code, README, key bindings, releases, change history, and MIT license are available on GitHub.
Technical environmentLXC and LXD containers on Linux
ImplementationRust, Ratatui, and Tokio
Source and licensePublic on GitHub · MIT
The LXTUI example
Put container state and common actions in one operator view.
LXTUI talks to the LXD API. Instead of rebuilding a command for each container action, you select the resource, choose the action, and watch its status from the same terminal interface.
Change running state
Start, stop, or restart the selected container with direct keys or a context-aware action menu.
Create from an image
Select an available image and enter the required details without reconstructing the container-creation command.
Clone or delete
Apply the supported clone or delete action to the container currently selected in the interface.
Open a container shell
Enter a shell inside a running container without leaving the application to look up and type the command again.
Watch long-running operations
Keep operation progress visible while the terminal interface remains responsive.
The operator path
Turn a sequence of commands into a guided action.
The tool carries resource identity and current state forward so the operator does not have to reconstruct that context at every step.
Load
Read the containers and available information from the configured LXD socket or remote.
Select
Choose the container from a live list instead of copying its identifier into a new command.
Act
Run an action that is valid for the selected container and its current state.
Observe
See operation progress, refreshed container state, or diagnostic information in the same interface.
What this demonstrates
Your technical procedure can become a tool your operators can use directly.
Your environment does not have to use containers. FoleyBridge can apply the same pattern to the commands, APIs, records, and safeguards behind your recurring technical tasks.
Focused status view
Collect the identifiers, state, health, and resource information operators need before they act.
Guided operator actions
Replace memorized command syntax with named actions, required fields, current context, and visible results.
API and command connections
Use the supported interfaces already provided by your servers, appliances, platforms, or internal services.
Valid-state controls
Show or enable actions according to the resource selected and the state the underlying system reports.
Progress and diagnostics
Keep long-running operations, failures, and useful diagnostic details visible to the person handling them.
Tooling that fits the environment
Use a terminal interface when operators live in a shell, or another suitable interface when the users and operating conditions require it.
Your operator tool
Show us the terminal steps your team repeats.
Start with one technical procedure that takes too many commands, depends on copied identifiers, or is easy to perform against the wrong resource.
- The commands or API calls operators use today
- The systems, resources, and states the tool must recognize
- The values operators must look up, copy, calculate, or confirm
- The actions that require warnings, confirmation, or restricted access
- The progress, result, errors, and history operators need to see
- The host, network, identity, and permission constraints in the environment
The interface is built around the procedure. It can expose the common path clearly while leaving unusual or unrestricted administration to the underlying technical tools.
Inspect LXTUI
Run the example or review how it is built.
The current repository documents installation, permissions, custom sockets, LXD remotes, key bindings, and host requirements. Cargo is the recommended installation path shown in the README.
cargo install lxtui lxtui
Default socket
Run against a standard local LXD installation when your user has the required access.
LXD_SOCKET
Point LXTUI at the socket path used by your local configuration.
LXD remote
Use a remote already configured through the LXD client.
RUST_LOG
Set the requested logging level when you need additional failure information.
LXTUI can change container state. Review the selected container and maintain safeguards and backups appropriate to creation, deletion, and shell access.
Built for your operators
Which technical procedure should become a tool?
Tell us what your operators do now, which systems they touch, and where repeated commands or missing context cause trouble.
Describe the tool you need