Installation

Requirements

Loom LDAP Browser requires:

Terminal emulator with Unicode and color support
Operating system: Linux, macOS, or Windows

For the best experience, use a terminal with 256-color support and a monospace font with good Unicode coverage.

Installation methods

Prebuilt binaries
From source

Download prebuilt binaries

The easiest way to get started is to download a prebuilt binary for your platform.

Visit the releases page

Navigate to the GitHub Releases page and find the latest version.

Download for your platform

Download the appropriate binary for your system:

Platform	Architecture	Download
Linux	x86_64	`loom-ldapbrowser-linux-x86_64`
Linux	aarch64	`loom-ldapbrowser-linux-aarch64`
macOS	Intel	`loom-ldapbrowser-macos-x86_64`
macOS	Apple Silicon	`loom-ldapbrowser-macos-aarch64`
Windows	x86_64	`loom-ldapbrowser-windows-x86_64.exe`

Make it executable

On Linux and macOS, make the binary executable:

chmod +x loom-ldapbrowser-*

Move to your PATH

Move the binary to a directory in your PATH for easy access:Linux/macOS:

sudo mv loom-ldapbrowser-* /usr/local/bin/loom-ldapbrowser

Windows: Move the .exe file to a directory in your PATH, or add its location to your PATH environment variable.

Verify installation

Verify the installation by checking the version:

loom-ldapbrowser --version

Build from source with Cargo

Building from source gives you the latest features and allows you to customize the build.

Install Rust

Loom LDAP Browser requires Rust 1.80 or later.If you don’t have Rust installed, get it from rustup.rs:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

After installation, ensure Rust is up to date:

rustup update

Clone the repository

Clone the Loom LDAP Browser repository:

git clone https://github.com/trepidity/loom-ldapbrowser.git
cd loom-ldapbrowser

Build and install

Use Cargo to build and install the binary:

cargo install --path crates/loom-ldapbrowser

This compiles the project in release mode and installs the binary to ~/.cargo/bin/loom-ldapbrowser.

Make sure ~/.cargo/bin is in your PATH. Most Rust installations add this automatically.

Verify installation

Verify the installation by checking the version:

loom-ldapbrowser --version

Build for development

If you’re developing or testing changes, you can build without installing:

# Build in debug mode
cargo build --workspace

# Run directly
cargo run --bin loom-ldapbrowser

# Build in release mode for better performance
cargo build --release --workspace
./target/release/loom-ldapbrowser

Run tests

Verify everything works by running the test suite:

cargo test --workspace

Configuration directory

On first run, Loom LDAP Browser creates a configuration directory:

Linux/macOS: ~/.config/loom-ldapbrowser/
Windows: %APPDATA%\loom-ldapbrowser\

This directory contains:

config.toml - Main configuration file with connection profiles and settings
themes/ - Custom theme files (optional)

The configuration file is created automatically when you save your first connection profile. You can also create it manually before first run.

Command-line options

Loom LDAP Browser supports several command-line options:

loom-ldapbrowser [OPTIONS]

Options

Option	Short	Description
`--config <PATH>`	`-c`	Path to config file (default: `~/.config/loom-ldapbrowser/config.toml`)
`--host <HOST>`	`-H`	LDAP host to connect to (overrides config)
`--port <PORT>`	`-p`	LDAP port (overrides config)
`--bind-dn <DN>`	`-D`	Bind DN (overrides config)
`--base-dn <DN>`	`-b`	Base DN (overrides config)
`--help`	`-h`	Print help information
`--version`	`-V`	Print version

Examples

# Connect directly to a server
loom-ldapbrowser -H ldap.example.com -D "cn=admin,dc=example,dc=com" -b "dc=example,dc=com"

# Use custom config file
loom-ldapbrowser -c /path/to/config.toml

# Override config file host
loom-ldapbrowser -H ldap-staging.example.com

Command-line arguments override the first connection profile in your config file. This is useful for quick connections or testing.

Next steps

Quick start

Connect to your first LDAP server and start browsing

Get Started

User Guide

Features

Requirements

Installation methods

Download prebuilt binaries

Build from source with Cargo

Build for development

Run tests

Configuration directory

Command-line options

Options

Examples

Next steps

Quick start

Build docs developers (and LLMs) love

Get Started

User Guide

Features

​Requirements

​Installation methods

​Download prebuilt binaries

​Build from source with Cargo

​Build for development

​Run tests

​Configuration directory

​Command-line options

​Options

​Examples

​Next steps

Quick start

Build docs developers (and LLMs) love

Requirements

Installation methods

Download prebuilt binaries

Build from source with Cargo

Build for development

Run tests

Configuration directory

Command-line options

Options

Examples

Next steps