Skip to content

cal.com #1397

Closed as not planned
Closed as not planned

Description

@MickLesk

community-scripts/ProxmoxVE#1348

Application Name

Cal.com

Website

https://github.com/calcom/cal.com

Description

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
  • Seamless calendar integration (Google, Outlook, etc.)
  • Automated meeting scheduling and management
  • Team scheduling capabilities
  • Customizable booking pages
  • API support for integration with other services

The addition would benefit users who:

  • Need a privacy-focused scheduling solution
  • Want to avoid SaaS subscription costs
  • Require integration with existing self-hosted infrastructure
  • Need GDPR-compliant meeting management

Activity

  1. converted this from a draft issue on Feb 2, 2026
  2. MickLesk commented on Feb 2, 2026

    @MickLesk
    MemberAuthor

    @community-scripts/contributor free to pick

  3. moved this from Backlog / Ready to Pick to Progress (ProxmoxVED) in 🚀 Script Pipeline Overviewon Feb 2, 2026
  4. vhsdream commented on Feb 5, 2026

    @vhsdream
    Member

    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!

  5. MickLesk commented on Feb 5, 2026

    @MickLesk
    MemberAuthor

    Maybe i add an Request for an prebuild archive. I think this tool ist really useful. Maybe the maintainers agree

  6. tremor021 commented on Feb 6, 2026

    @tremor021
    Member

    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

  7. MickLesk commented on Feb 6, 2026

    @MickLesk
    MemberAuthor

    added as request: calcom/cal.diy#27696

  8. fccview commented on Feb 6, 2026

    @fccview

    @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

  9. tremor021 commented on Feb 6, 2026

    @tremor021
    Member

    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

  10. fccview commented on Feb 6, 2026

    @fccview

    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 :)

  11. fccview commented on Feb 6, 2026

    @fccview

    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

  12. moved this from Progress (ProxmoxVED) to Deferred in 🚀 Script Pipeline Overviewon Mar 25, 2026
  13. michelroegl-brunner commented on Jun 21, 2026

    @michelroegl-brunner
    Member

    Merged with #15274 in ProxmoxVE

  14. MickLesk commented on Jul 27, 2026

    @MickLesk
    MemberAuthor

    5 month no response, close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions