In Lightdash, everything you need for BI is written as code in your dbt project. You use dbt to transform all of the data from your data warehouse, then you use Lightdash to explore it.

But, before you hook up your dbt project to Lightdash, we need to make sure we have Tables to explore. In this setup guide, we’ll walk you through the steps of installing + using the Lightdash CLI and creating the first Tables in your project.

New to dbt? If you haven’t used dbt before, follow dbt’s getting started guidebefore proceeding with setting up Lightdash.

​
What are Tables?

Tables are the starting point to any data exploration in Lightdash - they’re the data in Lightdash that you can query. The beauty of Lightdash is that we’re pretty well synced with your dbt project. So, in Lightdash, Tables actually come from dbt models that have been defined in your dbt project’s .yml files.

If your dbt model has been defined in a .yml file, it will appear in Lightdash as a Table.

Not sure what a .yml file is? Make sure to check out dbt’s docs to learn more about building .yml files for your dbt project.

Here’s an example of our Community stats daily model we’ve defined in dbt. In Lightdash, we can see it in our list of available Tables to explore.

Now that we know what tables are, let’s add some and create our first project!

​
Step 1: Install the Lightdash CLI tool

The Lightdash CLI is the recommended way to develop your dbt + Lightdash project. It makes development faster and easier, as well as giving you options for building more powerful automation to manage your Lightdash instance.

Before installing Lightdash CLI, you need to have NodeJS/NPM installed on your machine. To check that, run the following command in your terminal:

node -v; npm -v;
# it should print something like:
# v20.8.0
# 8.15.0

Run the following on your terminal to install the Lightdash CLI.

npm install -g @lightdash/cli

If you get an npm ERR! code EACCES error while installing the Lightdash CLI, follow this guide to resolve it.

​
Step 2: Login to the CLI

We’ve automatically generated a personal access token that you can use to login to the CLI, so you just need to copy-paste that command in your Terminal.

It’s Step 2. and should look something like this:

lightdash login https://{{ lightdash_domain }} --token my-super-secret-token

Where {{ lightdash_domain }} is app.lightdash.cloud for Lightdash Cloud users. Or your own domain if self-hosting. If you want to login using another method, then you can check out our authentication methods here.

​
Step 3: Add Tables

If you’re using dbt Cloud, you’ll need to clone your repo to your local machine before completing the next steps.

To get our dbt project Lightdash-ready, we need to define all of the columns in our dbt models that we want to explore in Lightdash. We’ve made this really easy to do using our CLI tool and the command:

lightdash dbt run

This will generate Tables and dimensions for your entire dbt project. It will document all of the columns in your models and these are what we explore in Lightdash as Dimensions.

For example, if we have a projects.yml file, we’d have a Table called Projects and it would have the dimensions: Dashboards created num total and Days since project created.

If you’re getting an error: Error: Not a dbt project (or any of the parent directories). Missing dbt\_project.yml file

Make sure that you’re in your dbt project folder (i.e. where your dbt_project.yml file is) before you try doing lightdash dbt run

​
Step 4: Create your project

Now, your dbt project is Lightdash-ready! Just run this command and follow the link to start exploring your data:

lightdash deploy --create

​
Next steps: Update your project connection settings

We create your first project using your local dbt profiles.yml file. So, you might want to update your connection settings to:

  1. Set up a service account for Lightdash to run on (instead of using your personal connection details)

  2. Connect Lightdash to your version controlled dbt project so changes are automatically synced.

Check out details on updating your connection settings here.

Raise issue