![]() If you need to run the JAR in production, you should run Metabase as a service. If you’re running Metabase as a service, you’ll put these environment variables in a separate configuration file. The above command would connect Metabase to your Postgres database, metabaseappdb via localhost:5432 with the user account username and password password. You would get a PostgreSQL service up and running and create an empty database: Production application databaseįor example, say you want to use PostgreSQL. If you’d prefer to use Docker, check out running Metabase on Docker. ![]() Use a production application database to store your Metabase application data.The steps are similar to those steps above with two important differences: if you want to run Metabase in production, you’ll want to: If you want to run Metabase in production we recommend you migrate away from H2. This default is meant for simple evaluation or personal use. Note that in the default configuration Metabase will use a local H2 database for storing all its own application data. 06-19 10:29:34 INFO metabase.task :: Initializing task CheckForNewVersionsĠ6-19 10:29:34 INFO metabase.task :: Initializing task SendAnonymousUsageStatsĠ6-19 10:29:34 INFO metabase.task :: Initializing task SendAbandomentEmailsĠ6-19 10:29:34 INFO metabase.task :: Initializing task SendPulsesĠ6-19 10:29:34 INFO metabase.task :: Initializing task SendFollowUpEmailsĠ6-19 10:29:34 INFO metabase.task :: Initializing task TaskHistor圜leanupĠ6-19 10:29:34 INFO re :: Metabase Initialization COMPLETEĪt this point you’re ready to go! You can access your new Metabase server on port 3000, most likely at You can use another port than 3000 by setting the MB_JETTY_PORT environment variable before running the jar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |