Deploying Metabase to Scalingo
Deploying Using Scalingo's One-click Button
Click on the button below to deploy Metabase to Scalingo within minutes.
Deploying Using Scalingo's Command Line Tool
- Create an application on Scalingo:
$ scalingo create my-metabase
- Add a PostgreSQL for the internal usage of Metabase:
$ scalingo --app my-metabase addons-add postgresql postgresql-starter-512
- Configure your application to use the appropriate buildpack for deployments:
$ scalingo --app my-metabase env-set 'BUILDPACK_URL=https://github.com/Scalingo/multi-buildpack'
- Clone this repository:
$ git clone https://github.com/Scalingo/metabase-scalingo
- Configure
git
:
$ cd metabase-scalingo
$ scalingo --app my-metabase git-setup
- Deploy the application:
$ git push scalingo master
Configuring the Application Deployment Environment
The following environment variables are available for you to adjust, depending on your needs:
Name | Description | Default value |
---|---|---|
BUILDPACK_URL |
URL of the buildpack to use. | https://github.com/Scalingo/multi-buildpack.git |
DATABASE_URL |
URL of your database addon. Only available if you have a database addon provisioned. | Provided by Scalingo |
MAX_METASPACE_SIZE |
Maximum amount of memory allocated to Java Metaspace1. | 512m (512MB) |
Metabase also supports many environment variables.
Updating Metabase on Scalingo
To upgrade to the latest version of Metabase, you only need to redeploy it, this will retrieve the latest version avaible on the Metabase buildpack.
Updating After Deploying Using Scalingo's One-click Button
If you deployed your Metabase instance via our One-click button, you can update it with the following command:
$ scalingo --app my-metabase deploy https://github.com/Scalingo/metabase-scalingo/archive/refs/heads/master.tar.gz
Updating After Deploying Using Scalingo's Command Line Tool
$ cd metabase-scalingo
$ git pull origin master
$ git push scalingo master
Footnotes
-
See https://wiki.openjdk.org/display/HotSpot/Metaspace for further details about Java Metaspace. ↩