For production installations of Metabase we recommend that users replace the H2 database with a more robust option such as Postgres. This offers a greater degree of performance and reliability when Metabase is running with many users. When the application is first launched it will attempt to create a new H2 database in the same filesystem location the application is launched from. If for any reason you want to use an H2 database file in a separate location from where you launch Metabase you can do so using an environment variable.
For example:. Note that H2 automatically appends. You can change the application database to use Postgres using a few simple environment variables. Environment variables provide a good way to customize and configure your Metabase instance on your server.
Some Metabase configs have available options, some of which are shown below, separated by symbols:. 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. We only have a few more quick steps to finish registering our service and having Metabase up and running.
Note: The nginx. Propose a change on the source. Need a different version of the docs? See the available versions. Did this article help you? For example the syslog db from all my server and syslog from my firewall contains a lot of logs but 17 GB is a lot of data only for metabase. I have been watching the trace file for a few months now. No more bloating! What these files are metabase. Thanks, Sridhar. AndrewMBaines April 17, , am 2.
0コメント