helm chart custom values input

[tiina303]

Hi, I’m trying to bring Posthog to the marketplace via a helm chart.
Minimally for Posthog to work nicely I’d need:

1. hostname (for tls, cert manager, what they will use as the UI), which they need to register and point to the LB IP
2. outgoing email smtp login and password (used for password reset etc)

I saw these two issues:

• helm chart / stack parameter #34
• Update CONTRIBUTING.md guide to include how deploy-time config is set. #57 (couldn’t find anything in contributing.md)

Since our charts repo is open source anyone could use that directly already to create the k8s cluster on DigitalOcean, customize their values file & deploy via helm. But I’d love to have a 1-click deployment via marketplace, I’m just not sure how to get these two parameters from users.

[keladhruv]

Hi @tiina303,
Thank you for opening this issue!
As of today we do not support this, but I will keep you informed if there are any developments on this end.

[tiina303]

Thanks for the info. It would be awesome for DigitalOcean to support this. In our other deployment options (gcp marketplace and Heroku) we are using user provided parameters.

[fuziontech]

This would be 10/10 awesome if you did support it.

[jgannondo]

@tiina303 thanks for this feedback.

Related to:

outgoing email smtp login and password (used for password reset etc)

Can you elaborate on that one? I think I understand what you mean but I wanted to make sure I was clear. Thanks!

[tiina303]

Outgoing email

I mentioned password reset, let me elaborate a bit on that:
If someone hosts Posthog on DigitalOcean, it will be accessible to their users (people in their organization also looking at analytics) through their hostname/domain (hence the need for the hostname parameter).
Now the first page users get sent to is the login page (similar to what you see when visiting https://app.posthog.com/).
As you can see we have a "forgot your password?" that links to where users can reset passwords, which is where we'd use the provided email credentials.

I have a somewhat parameters related question: where is the upgrade.sh script used. We had to provide it, but I haven't seen any way on the website to do an upgrade to the installed app.

[fuziontech]

For the email example, this is basically to help us avoid moving those configs into the database which we'd like to avoid. It's not a deal breaker, but very nice to have.

As for the hostname, this is more critical. That is for the helm chart and needs to be defined at creation. We really want this to be as turn key as possible with TLS. The only way we can do that is by having the user provide the domain name at creation so that we can configure let's encrypt to grab a cert for that domain once the IP of the LB is setup on it. If there is a better way for us to go about this let us know! We just want to push everyone towards TLS as much as possible.

[tiina303]

Hi, is there's any chance providing parameters will be possible in the near future? I'm following up because doing the TLS steps manually is significantly more complicated compared to if our users could provide a single string parameter (see https://posthog.com/docs/self-host/deploy/digital-ocean#securing-your-1-click-install) and we regularly get questions where something went wrong.