Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes Support #22

Closed
marziman opened this issue Apr 15, 2021 · 8 comments
Closed

Kubernetes Support #22

marziman opened this issue Apr 15, 2021 · 8 comments
Labels
✨ feature New feature or request

Comments

@marziman
Copy link

I will be starting working on Kubernetes Support. Adding this issue so everbody can follow up here.

@PeerRich PeerRich added the ✨ feature New feature or request label Apr 15, 2021
@bashfulrobot
Copy link

I'm mostly just commenting to follow this. 👍

@kav
Copy link

kav commented May 19, 2021

Any notes on what you need here? Looks like at the moment it's just a stateless nodejs app. We've got a respectable if a bit bare helm chart for that here: https://github.com/pelotech/charts/tree/main/charts/nodejs
The bitnami folks have a comprehensive if slightly overkill chart here
https://github.com/bitnami/charts/tree/master/bitnami/node
Though as overkill as it is you might be able to point it at the repository and be good to go.

@kav
Copy link

kav commented May 19, 2021

Ah looks like it also has a postgres dep, the bitnami chart for that is also excellent, so might just need to require those two, https://github.com/bitnami/charts/tree/master/bitnami/postgresql
Happy to help out if you'd like

@aldenjenkins
Copy link

Following

@baileypumfleet
Copy link
Contributor

I'm going to close this off because there hasn't been any movement on this. Happy to reopen if someone implements a community-supported version of Calendso on Kubernetes

@skadefro
Copy link

skadefro commented Jan 9, 2022

I've started implementing a helm chart for calendso at https://github.com/open-rpa/helm-charts/tree/main/charts/calendso
But keep running into the issue with some environment variables not getting picked up by next.js like others have reported.
( I can make stripe payments, i can define mail-, google api-, db- settings but BASE_URL or NEXT_PUBLIC_BASE_URL or NEXT_PUBLIC_APP_URL seem to not work ( it keeps saying localhost3000 ) and NEXT_PUBLIC_LICENSE_CONSENT does not work either.
Is there any ETA on when this gets fixed ?

@tomlobato
Copy link

tomlobato commented Apr 5, 2022

I've started implementing a helm chart for calendso at https://github.com/open-rpa/helm-charts/tree/main/charts/calendso But keep running into the issue with some environment variables not getting picked up by next.js like others have reported. ( I can make stripe payments, i can define mail-, google api-, db- settings but BASE_URL or NEXT_PUBLIC_BASE_URL or NEXT_PUBLIC_APP_URL seem to not work ( it keeps saying localhost3000 ) and NEXT_PUBLIC_LICENSE_CONSENT does not work either. Is there any ETA on when this gets fixed ?

Same here.
Found #1160 (comment) and https://github.com/calcom/docker.
Look at 'Important Notes' at last link. Until we have NEXT_PUBLIC_* vars being read at runtime we need to build our own private docker images.

@krumware
Copy link
Member

This is something that is very much on the radar over at https://github.com/calcom/docker, including the push for runtime variables

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

No branches or pull requests

9 participants