Skip to content

Conversation

nicopace
Copy link

@nicopace nicopace commented Aug 5, 2025

Implements #17 .

@nicopace nicopace linked an issue Aug 5, 2025 that may be closed by this pull request
@nicopace
Copy link
Author

nicopace commented Aug 5, 2025

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
Copy link
Contributor

IamJeffG commented Aug 5, 2025

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

This is correct.

Copy link
Contributor

@IamJeffG IamJeffG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a one-click app for Metabase
3 participants