Reposted from Upwork
Overview:
We want to have a production ready Metabase instance on our Google Compute Engine VM
We tested implementation accordingly to these instructions https://jonathan-holloway.medium.com/deploying-metabase-on-google-cloud-platform-gcp-95a8010f9a93
All is good. Metabase was available via ssh on localhost/3000
But it is not what we want to show the client.
Challenge #1
Make self-hosted Metabase available publicly on our domain. So instead of ssh and localhost/3000 we can just visit a browser page like https://kwantyx-data.com, login and build/view dashboards
It requires some reverse proxy set up in Google Cloud. We are looking for the best solution.
Challenge #2
Since we want it to be production ready an application database (to store questions, dashboards, and users) should be not in the docker container but, for example, in Cloud SQL.
Metabase provides instructions how to do it, but it is not clear how to apply to a docker image running on the Compute Engine.
Apply or learn more here: https://www.upwork.com/freelance-jobs/apply/Install-Metabase-Google-Compute-Engine_~01e520726635f27523/