lakefront 0.1.2

Lakehouse Observability Platform

Lakefront

A terminal-based lakehouse observability platform for exploring and managing data sources from your command line.

---

About

Working with lakehouse data — Parquet files on local disk or S3, DuckDB queries, materialized views — usually means jumping between tools, writing throwaway scripts, or wrestling with heavyweight UIs. Lakefront puts it all in one place: a fast TUI and CLI for data engineers who live in the terminal.

Problems it solves:

• No single tool for lakehouse exploration — Lakefront combines DuckDB-powered SQL querying, S3 source management, and dataset browsing in one cohesive interface.
• Configuration sprawl — profiles let you switch between environments (local dev, staging, production S3) with a single command, keeping credentials out of your scripts.
• Context switching — instead of firing up a Jupyter notebook or a GUI just to peek at a Parquet file, you stay in the terminal.

---

Examples

Initialise Lakefront

Bootstrap the ~/.lakefront directory structure and create a default profile:

uv run lakefront init

Config Management

# List all profiles
uv run lakefront config list

# Show config directories and paths
uv run lakefront config info

# Create a new profile
uv run lakefront config create --profile staging

# Inspect a profile's current settings
uv run lakefront config inspect --profile staging

# See which profile is active
uv run lakefront config get-active

# Switch to a different profile
uv run lakefront config set-active --profile staging

Secrets (S3 access keys etc.) are never written to the TOML profile — set them via environment variables instead:

export LAKEFRONT_S3__ACCESS_KEY=...
export LAKEFRONT_S3__SECRET_KEY=...

---

Project Structure

pkg/
├── core/   # DuckDB logic, config models, settings
├── cli/    # Typer entrypoint and sub-commands
└── tui/    # Textual TUI app (in progress)