You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cal.com (formerly Calendly) is an open-source scheduling infrastructure and meeting management platform that would make a valuable addition to the Helper-Scripts collection.
Key Benefits:
Self-hosted alternative to Calendly with full control over data
I was investigating this a bit in the past and kept running into OOM during the build. Then a couple days ago I tried building it again, adding NODE_OPTIONS="--max-old-space-size=6144" to an 8GB and 6CPU test LXC, and it took ages to build (like 20+ minutes). This one will be a major PITA for whoever takes it!
I was investigating this a bit in the past and kept running into OOM during the build. Then a couple days ago I tried building it again, adding NODE_OPTIONS="--max-old-space-size=6144" to an 8GB and 6CPU test LXC, and it took ages to build (like 20+ minutes). This one will be a major PITA for whoever takes it!
This was my experience also, hence why i left it alone for a while.
@MickLesk can you ask for a prebuild on this then? if they can do that, it will save us ton of headaches
@MickLesk I was thinking about what you told me the other day that a lot of developers of apps you include in your scripts just don't help with support and it got my gears spinning.
I don't know if they will make a tarball for you, I'm talking more in general right now, we could have a pipeline running every 3/4 hours that builds tarballs for problematic apps taken from latest releases.
As long as you opensource it the github actions should stay free lol
Sadly, not all developers like to deviate from their original vision of how their app will be released/distributed. Some see a potential and help us, some don't. It is what it is....
I mean, if we can't make it work we will just not waste more time on it. It does look like a cool project though
Sadly, not all developers like to deviate from their original vision of how their app will be released/distributed. Some see a potential and help us, some don't. It is what it is....
I understand that indeed, which is why I'm suggesting that maybe the tarball should be just created by our own pipelines if the developers decide to decline the request, it shouldn't be too hard to build a system that automatically creates tarball for various projects, I'll have a look :)
Phew I take it back, I managed to make a system that takes the latest release and builds it in a tarball but they have so many env variabes to be set on build time, some of which should be user defined, I am not sure they can realistically provide a tarball given that on build time and run time you need to provide the same encryption key, unless they make a tarball with a public encryption key? 🤷
Will take a step back and wait for their response <3
Activity
MickLesk commentedon Feb 2, 2026
@community-scripts/contributor free to pick
vhsdream commentedon Feb 5, 2026
I was investigating this a bit in the past and kept running into OOM during the build. Then a couple days ago I tried building it again, adding
NODE_OPTIONS="--max-old-space-size=6144"to an 8GB and 6CPU test LXC, and it took ages to build (like 20+ minutes). This one will be a major PITA for whoever takes it!MickLesk commentedon Feb 5, 2026
Maybe i add an Request for an prebuild archive. I think this tool ist really useful. Maybe the maintainers agree
tremor021 commentedon Feb 6, 2026
This was my experience also, hence why i left it alone for a while.
@MickLesk can you ask for a prebuild on this then? if they can do that, it will save us ton of headaches
MickLesk commentedon Feb 6, 2026
added as request: calcom/cal.diy#27696
fccview commentedon Feb 6, 2026
@MickLesk I was thinking about what you told me the other day that a lot of developers of apps you include in your scripts just don't help with support and it got my gears spinning.
I don't know if they will make a tarball for you, I'm talking more in general right now, we could have a pipeline running every 3/4 hours that builds tarballs for problematic apps taken from latest releases.
As long as you opensource it the github actions should stay free lol
tremor021 commentedon Feb 6, 2026
Sadly, not all developers like to deviate from their original vision of how their app will be released/distributed. Some see a potential and help us, some don't. It is what it is....
I mean, if we can't make it work we will just not waste more time on it. It does look like a cool project though
fccview commentedon Feb 6, 2026
I understand that indeed, which is why I'm suggesting that maybe the tarball should be just created by our own pipelines if the developers decide to decline the request, it shouldn't be too hard to build a system that automatically creates tarball for various projects, I'll have a look :)
fccview commentedon Feb 6, 2026
Phew I take it back, I managed to make a system that takes the latest release and builds it in a tarball but they have so many env variabes to be set on build time, some of which should be user defined, I am not sure they can realistically provide a tarball given that on build time and run time you need to provide the same encryption key, unless they make a tarball with a public encryption key? 🤷
Will take a step back and wait for their response <3
michelroegl-brunner commentedon Jun 21, 2026
Merged with #15274 in ProxmoxVE
MickLesk commentedon Jul 27, 2026
5 month no response, close