Add Metabase one-click-app.

[nicopace]

Implements #17 .

[nicopace]

As this is my first caprover instance that needs state backed by a database, I just found out (or maybe it was in my mind but completely lost) that we need to setup the database credentials and authentication manually for every service that gets deployed in GC.
Is this right? Or am I missing a step where we can ask caprover for a db, and caprover somehow deals with that with whatever database it is setup with?

I ask this because another caprover-like system i used to use, yunohost, does this database management for the apps... so when you create this specs you get the database from the platform.

[IamJeffG]

we need to setup the database credentials and authentication manually for every service that gets deployed in GC

This is correct.

[IamJeffG]

Can the upstream one-click definition for metabase meet our needs? If so I'd prefer not to maintain our own.

https://github.com/caprover/one-click-apps/blob/master/public/v4/apps/metabase.yml

(That said I acknowledge sometimes there are reasons we can't use the upstream one...)

[rudokemper]

It seems that the upstream definition deploys its own Postgres. So this would seem to be another one of those cases where we maintain our own metabase-only definition like we do for Superset and Windmill.

[IamJeffG]

This is wild to me that simply running a fresh metabase docker container consistently uses 1GB of RAM on the host. That's before initial setup, i.e choosing your language, hooking it up to any database ...

Metabase is a cool tool but should be deployed with caution. :-)