By default, backend database (H2) is stored inside container, and will be lost after container restart. So we highly recommended to use MySQL or Postgres instead. Copy these default configuration into a new file named metabase-config.yaml, then modify as your need. Deploy Metabase using your config file. We would like to show you a description here but the site won’t allow us.
v0.39.0.1 / Operations Guide / Installing Metabase
Metabase is built and packaged as a Java jar file and can be run anywhere that Java is available. Below we provide detailed instructions on how to install and run Metabase in a variety of common configurations.
Metabase Kubernetes Helm
Running the Jar File
This is the simplest and most basic way of running Metabase. Here we’ll cover the general requirements for running Metabase and provide some information about how to customize your installation for any scenario.
Running the Mac Application
Metabase provides a binary Mac OS X application for users who are interested in trying Metabase on a Mac system.
Metabase On Kubernetes Cloud
Running on Docker
If you are using Docker containers and prefer to manage your Metabase installation that way then we’ve got you covered. This guide discusses how to use the Metabase Docker image to launch a container running Metabase.
Running on AWS Elastic Beanstalk
Step-by-step instructions on how to deploy Metabase on Elastic Beanstalk using RDS. This is the most common way to run Metabase in production.
Metabase On Kubernetes Python
Running on Heroku
Currently in beta. We’ve run Metabase on Heroku and it works just fine, but it’s not hardened for production use just yet. If you’re up for it then give it a shot and let us know how we can make it better!
Running on Debian as a service
Community support only at this time, but learn how to deploy Metabase as a service on Debian (and Debian-based) systems. Simple, guided, step-by-step approach that will work on any VPS.
Running on Kubernetes
Community Helm chart for running Metabase on Kubernetes