

If you don't have your database properly configured, Metabase won't be able to start. These values should match what you've set in your Metabase config for the MB_DB_TYPE, MB_DB_DBNAME, MB_DB_USER, and MB_DB_PASS environment variables. If you're running postgres or some other database, you need to ensure you've already followed the instructions for your database system to create a database for Metabase, as well as a user that can access that database. We only have a few more quick steps to finish registering our service and having Metabase up and running. The best part of setting up Metabase as a service on a Debian-based system is to be confident it will start up at every system boot. # any other env vars you want available to Metabase

Some Metabase configs have available options, some of which are shown below, separated by | symbols: #!/bin/sh In /etc/default/metabase, replace configurable items (they look like ) with values sensible for your system. The Metabase config fileĬreate your /etc/default/metabase environment config file and open it in your editor: $ sudo touch /etc/default/metabase On Debian systems, services typically expect to have accompanying configs inside etc/default/. "Įcho "Notice: log file is not be removed: '$LOGFILE'" >&2Įcho "Usage: $0 "Įnvironment variables provide a good way to customize and configure your Metabase instance on your server. Kill -15 $(cat "$PIDFILE") & rm -f "$PIDFILE"Įcho -n "Are you really sure you want to uninstall Metabase? That cannot be undone. # run our Metabase cmd as unprivileged user # load Metabase config before we start so our env vars are available Local CMD="nohup java -jar \"$METABASE\" &> \"$LOGFILE\" & echo \$!" # execute the Metabase jar and send output to our log # where should we store the pid/log files? # which (unprivileged) user should we run Metabase as? # where will our environment variables be stored? # Description: Metabase analytics and intelligence platform


# Required-Stop: $local_fs $network $named $time $syslog # Required-Start: $local_fs $network $named $time $syslog The Metabase script below has extra comments to help you know what everything is for. In /etc/init.d/metabase, replace configurable items (they look like ) with values sensible for your system. The Metabase service fileĬreate the /etc/init.d/metabase service file and open it in your editor: $ sudo touch /etc/init.d/metabase So, a Metabase service should live at /etc/init.d/metabase. Services are typically registered at etc/init.d/.
#Metabase alerts how to#
