getlago / lago-helm-charts Goto Github PK

please publish this helm chart, so others can use it easily via helm.

there is a gh action that supports publishing helm charts via gh pages.

https://helm.sh/docs/howto/chart_releaser_action/

You must specify that the end user's Ingress should add the appropriate CORS headers, or you should propagate the configuration to the API server from values.yaml, to ensure that the frontend URL is correctly CORS-enabled.

For the Ingress corresponding to the API, these nginx location snippets address the issue

add_header 'Access-Control-Allow-Origin' 'https://frontendurl.yourdomain.com';
add_header 'Vary' 'Origin';
add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, OPTIONS';
add_header 'Access-Control-Allow-Headers' 'DNT,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,apollographql-client-name,apollographql-client-version,x-lago-organization,customer-portal-token';

via apollographql/apollo-client#4164

How can I deploy Lago on on-premise kubernetes cluster ?

Here is what I get when I tried to enable smtp. I filled out the detail such as address, username, fromEmail, etc. But an error was shown in port.

Here is the value:

smtp:
    enabled: true
    address: smtp.mydomain.com
    port: 587
    username: [email protected]
    password: mySMTPpassword
    fromEmail: [email protected]

Screenshot attached.

Can you provide any information about the shared volume which is mounted at /app/storage?

What kind of data is stored in there? why is it needed to be shared across all pods of lago-api deployment and lago-worker deployment?
We are using Longhorn as a storage backend and therefor need to avoid PersistentVolumeClaims in RWX mode.

Thanks in advance for clarification.

These should look like:

apiUrl: https://lago-api.yourdomain.com
frontUrl: https://frontend.yourdomain.com

not apiUrl: lago-api.yourdomain.com. Otherwise the front end attempts to post to frontend.yourdomain.com/lago-api.yourdomain.com.

Additionally, trying to do https://frontend.yourdomain.com fails too.

In order to store secrets safely in a public or private Git repository there is Bitnami’s sealed-secrets controller or Mozilla’s SOPS.

But I can not use a such mechanism, because the secret in this helm-chart is always installing this chart.

It could be nice to have an option via values.yaml to enable / disable creating this secret.

When trying to run the helm chart with my own Postgresql instance, I'm getting the following

URI::InvalidURIError: bad URI(is not URI?): postgresql://lago:[email protected]:5432/lago (URI::InvalidURIError)

I've removed special characters from my password and it works fine. This suggests some escaping might be happening in an ENV var (at a guess).

The password it shows in the error macthes what I have so it's correct in the URI.

Looking further into it, it seems similar to the last comment in this thread.
https://stackoverflow.com/questions/28976639/undefined-method-default-timezone-for-activerecordbaseclass-on-ubuntu-14

I suspect this issue probably needs moving upstream into one of the other lago repos but this is where I hit it so thought I'd raise it here,.

Hey, I downloaded the helm package. and tried to install it, but I'm consistently having two issues:

1. Error: INSTALLATION FAILED: create: failed to create: Secret "sh.helm.release.v1.billing.v1" is invalid: data: Too long: must have at most 1048576 bytes
2. Error: INSTALLATION FAILED: create: failed to create: Request entity too large: limit is 3145728

Can anyone please elaborate how to fix this problem? In the past, I did helm install Lago he v1.0.0 successfully, but when I just tried to install from this repo I'm having this issue

Hey, I downloaded the helm package. and tried to install it, but I'm consistently having two issues:

1. Error: INSTALLATION FAILED: create: failed to create: Secret "sh.helm.release.v1.billing.v1" is invalid: data: Too long: must have at most 1048576 bytes
2. Error: INSTALLATION FAILED: create: failed to create: Request entity too large: limit is 3145728

Can anyone please elaborate how to fix this problem? In the past, I did helm install Lago he v1.0.0 successfully, but when I just tried to install from this repo I'm having this issue