![]() ![]() ![]() For this, we are creating a Webhook Relay tunnel that will be established by a webhookrelayd container. Our Metabase deployment will need to be reachable from outside so we can actually view reports. Create a Webhook Relay tunnel for your Metabase app Once you run the command, after a few seconds (depends on your internet speed) you should see the magic happen and device appear in your "Devices" page in Synpse :)Ģ. There are multiple ways to do it however initially you can just SSH into the machine via local network. From there you will be able to find the auto-generated command that you need to run on the device to add it to your project. Once you log into Synpse Cloud, select your project and then head to the "Devices" page. Offers management of up to 5 devices free of charge.ġ. Synpse account - a lightweight and fantastic platform to manage and run software on your own hardware.Webhook Relay account - will be used to expose the Metabase to the internet, so we can access it.In this article, we will use a setup that works exactly the same way on both an Intel NUC (for some of my projects) and on a large VM that is managed by a VMware. Stability - managed instances can be updated at any time and can break your setup.Privacy - since you need to supply connection strings to your detabase, it's much better to do it on your own hardware where you control the risks.I have mine for more than 2 years and it's been fantastic little helper. Costs - hardware like Intel NUC (or new ones from AMD) pay for themselves not in years but in months.Performance - compared to Cloud VMs your own hardware will not be throttled even when it runs heavy queries.Main benefits of self-hosting Metabase (other tools as well): When paired with the right technologies, this setup becomes trivial to any small or large organizations. I personally am a fan of Metabase as it is the easiest to deploy and use. NOTE: the database I use is AWS RDS, just to make sure that it's not related with AWS.It is always useful to know how your business or projects are doing and for that, there are a bunch of tools available such as Excel spreadsheets, Google DataStudio, Apache Superset, etc. NOTE: I have tried to drop all the table and start with fresh schema multiple times and it didn't work as well. In the issue page they suggest: java -jar metabase.jar migrate force. On further searches I found a similar issue in github stating that "Table 'core_organization' already exists", however, they claim that it is already fixed but I'm still having the issue. I get the exactly same error as with the compose file. e "MB_DB_HOST=secrethost" -name metabase metabase/metabase:v0.39.1 e "MB_DB_PORT=3306" -e "MB_DB_USER=secretuser" -e 'MB_DB_PASS=secretpass' \ I also tried to run directly without using compose file using this command: docker run -d -p 3000:3000 -e "MB_DB_TYPE=mysql" -e "MB_DB_DBNAME=metabase" \ Metabase_1 | 08:27:59,109 INFO re :: Metabase Shutting Down. Metabase_1 | at .(AbstractQueryProtocol.java:256) Metabase_1 | at .(AbstractQueryProtocol.java:1513) Metabase_1 | at .(AbstractQueryProtocol.java:1550) Metabase_1 | at .(AbstractQueryProtocol.java:1688) Metabase_1 | Caused by: : Table 'core_organization' already exists Metabase_1 | Reason: : (conn=32027) Table 'core_organization' already exists Metabase_1 | : Migration failed for change set migrations/000_migrations.yaml::1::agilliland: metabase_1 | 08:27:59,084 ERROR re :: Metabase Initialization FAILED When I run docker-compose up I get the following error. Here is the docker-compose.yml file I used to run metabase: # docker-compose.yml I read the documentation about running metabase with docker from here and setting metabase up with mysql from here and followed all the instruction as per the documentation. ![]()
0 Comments
Leave a Reply. |