Installation
LineageBridge offers multiple installation paths depending on your needs—from a zero-setup one-liner for quick evaluation to a full development environment.
🚀 Recommended: One-Line Quickstart
Fastest way to try LineageBridge:
curl -fsSL https://raw.githubusercontent.com/takabayashi/lineage-bridge/main/scripts/quickstart.sh | bash
This automatically:
- ✅ Installs all dependencies (no Python setup needed)
- ✅ Launches the UI with demo data
- ✅ Opens your browser
- ✅ Works on macOS, Linux, and WSL
Perfect for: First-time users, demos, evaluation
See the Quickstart Guide for the full walkthrough.
Alternative: Manual Installation
Choose manual installation when you need to:
- Develop or extend LineageBridge
- Customize the installation
- Work in an air-gapped environment
- Integrate with existing tooling
Prerequisites
System Requirements:
- Python 3.11+ (
python --versionto check) - Git
- 4GB RAM minimum
- Internet access (for API calls)
Confluent Cloud: (optional for demo mode)
- Account at confluent.cloud (free trial available)
- At least one Kafka cluster
- Cloud API key (OrgAdmin or EnvironmentAdmin)
Data Catalogs: (optional)
- Databricks UC: Workspace URL + token
- AWS Glue: AWS credentials with Glue permissions
- Google Data Lineage: GCP project + Data Lineage API enabled
Installation Steps
We use uv for development—it's blazing fast and handles dependencies beautifully.
First, install uv if you don't have it:
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
# Or use pip
pip install uv
Then install LineageBridge:
# Clone the repo
git clone https://github.com/takabayashi/lineage-bridge.git
cd lineage-bridge
# Basic installation
uv pip install -e .
# Or with dev tools (recommended if you'll be contributing)
uv pip install -e ".[dev]"
# Or with everything (dev + docs)
uv pip install -e ".[dev,docs]"
Why the -e flag?
Editable mode means changes to source code take effect immediately—no reinstalling needed. Handy for tinkering!
Good old pip works perfectly fine if you don't want to install uv.
For the fastest setup, use our Makefile (requires make installed):
# Clone the repo
git clone https://github.com/takabayashi/lineage-bridge.git
cd lineage-bridge
# One command to rule them all
make install
This automatically:
- Creates a virtual environment if needed
- Installs the package with dev dependencies
- Sets up all CLI entry points
Prefer containers? We've got you covered.
# Clone the repo
git clone https://github.com/takabayashi/lineage-bridge.git
cd lineage-bridge
# Build all images
make docker-build
# Or build manually
docker compose -f infra/docker/docker-compose.yml build
See Docker Installation below for running instructions.
Verify Everything Works
Let's make sure the installation succeeded.
# Check CLI tools are available
lineage-bridge-extract --help
lineage-bridge-watch --help
lineage-bridge-api --help
# Check the package version
python -c "from lineage_bridge import __version__; print(__version__)"
You should see version 0.4.0 (or higher). If all commands work, you're good to go!
Docker Installation
If you prefer containers, we provide pre-built Docker images for all components.
Prerequisites
You'll need Docker 20.10+ and Docker Compose 2.0+.
Run with Docker
Here's how to run each component:
# Using Makefile
make docker-ui
# Or manually
docker compose -f infra/docker/docker-compose.yml up ui
Open http://localhost:8501 to access the UI.
Don't Forget Credentials
Docker reads from your .env file in the project root. Make sure it's set up before running containers. See Configuration for details.
Next Steps
Installation done! Now let's get your credentials configured and extract some lineage.
- Configuration → - Set up your API credentials
- Quickstart → - Extract your first lineage graph
Troubleshooting
Python Version Issues
If you see Python version errors:
# Check what you're running
python --version
# Tell uv to use a specific Python version
uv pip install --python=3.11 -e .
Virtual Environment Issues
Prefer to manage your own virtual environment? No problem:
# Create and activate a venv
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
# Then install normally
pip install -e ".[dev]"
Permission Errors
Getting permission denied errors on macOS/Linux? Don't use sudo. Use a virtual environment instead:
# Create a venv first
python -m venv .venv
source .venv/bin/activate
# Now install
pip install -e ".[dev]"
Import Errors
If Python can't find the package after installation:
# Make sure you're in the right directory
cd lineage-bridge
# Reinstall in editable mode
pip install -e .
Still Stuck?
Check out the full Troubleshooting Guide or open an issue on GitHub.