This doc will show you how you can build and run Metabase on your own computer so you can play around with it or test features in development. You can also run development branches of Metabase using a pre-built Docker image.
If you’re using macOS, you’ll want to install Xcode Command Line Tools first, by running:
To complete any build of the Metabase code, you’ll need to install the following.
Clojure (https://clojure.org) - install the latest release by following the guide depending on your OS
Java Development Kit JDK (https://adoptopenjdk.net/releases.html) - you need to install JDK 11 (more info on Java versions)
Node.js (http://nodejs.org/) - latest LTS release
Yarn package manager for Node.js - latest release of version 1.x - you can install it in any OS by running:
npm install --global yarn
On a most recent stable Ubuntu/Debian, all the tools above, with the exception of Clojure, can be installed by using:
sudo apt install openjdk-11-jdk nodejs && sudo npm install --global yarn
If you have multiple JDK versions installed in your machine, be sure to switch your JDK before building with:
sudo update-alternatives --config java
Then select Java 11 in the menu.
If you are developing on Windows, you should run Ubuntu on Windows Subsystem for Linux (WSL) and follow instructions for Ubuntu/Linux.
Alternatively, without the need to explicitly install the above dependencies, follow the guide on using Visual Studio Code and its remote container support.
Once you’ve installed all the build tools, you’ll need to clone the Metabase repository from GitHub.
Create a workspace folder (you can name it that or whatever you want), which will store the Metabase code files.
Open up your terminal app, and navigate to your workspace folder with:
git clone https://github.com/metabase/metabase
This is the part that you’ll use over and over.
The “official” branch of Metabase is called master, and other feature development branches get merged into it when they’re approved. So if you want to try out a feature before then, you’ll need to know the name of that branch so you can switch over to it. Here’s what to do:
Open up your terminal app
Navigate to where you’re storing the Metabase code. If you followed this guide exactly, you’d get there by entering this command:
“Pull” down the latest code by running:
You should do this every time to make sure that you have all the latest Metabase branches and code on your computer. It’s also how you’ll get updates on a feature branch someone make changes to it.
Find the name of the branch you want to run by going to the “pull request” page for that feature on GitHub and copying the branch name from there. Here’s an example PR page, with the branch name
Switch to, or “check out,” that branch by running:
git checkout <branch-name>
If we wanted to switch to the branch in the previous step, we’d run:
git checkout fix-native-dataset-drill-popover
When you want to switch back to master, run:
git checkout master
Now we’ll start up the backend server of Metabase with:
When it’s done, you should see a message that says something like “Metabase initialization complete.” Keep this tab in your terminal app running, otherwise it’ll stop Metabase.
Open up another tab or window of your terminal app, and then “build” the frontend (all the UI) with this command:
This is the local “server” on your computer, and 3000 is the “port” that Metabase is running on. You can have multiple different apps running on different ports on your own computer. Note that if you share any URLs with others that begin with localhost, they won’t be able to access them because your computer by default isn’t open up to the whole world, for security.
To switch to a different branch or back to master, open up another Terminal tab, and repeat steps 6, 7, and 8. If Metabase wasn’t already running, you’ll need to complete steps 9 and 10 again too. If it was already running, the frontend will automatically rebuild itself. You can check its progress by switching to that tab in your Terminal — it usually takes something like 15 seconds, but will depend on your hardware.
If you want to make Metabase stop running, you can either quit your terminal program, or go to the tab with the backend running and hit Ctrl+C to stop the backend. Most of the time you don’t have to do this to switch branches, but there are some cases where the change or feature you’re trying to see is a change with the backend, and you may need to stop the backend with Ctrl+C and then restart it by completing step 9 again.
The entire Metabase application is compiled and assembled into a single .jar file which can run on any modern JVM. There is a script which will execute all steps in the process and output the final artifact for you. You can pass the environment variable MB_EDITION before running the build script to choose the version that you want to build. If you don’t provide a value, the default is oss which will build the Community Edition.
After running the build script simply look in target/uberjar for the output .jar file and you are ready to go.
Did this article help you?
Thanks for your feedback!