Cal.com (was Calendso) - Calendly Alternative
-
@LoudLemur no, cal.com is the new name for calendso
-
Hello folks, anyone with some news on this? They just released version 2.0
-
Would love to have this as well. Please make it happen
-
@mabaker @chetbaker I am working on this happy to join up and hack together on it. If you wanna hack on this with me just set a time on my calendar and we can work on it. https://short.draglabs.com/cal
-
@roofboard I’m not a developer, but happy to test out when there’s any unstable self hosted implementation.
-
@roofboard great news, thanks! Hopefully @staff or @appdev can help out too!
-
Would love to see support for Cal.com as well!
-
I have made some progress here apparently calcom needs access to a database while running yarn build, and while running yarn it would be writing to /app/code
So I created a temporary database so long as you build this on a server with access to postgres this will work. The only problem is that I cannot figure out why it is stuck on localhost:3000 as opposed to accepting the new dns settings
https://git.draglabs.com/davidjstrom/cloudron-calcom-v2/-/tree/localhost-issue
@girish
Any thoughts? -
@roofboard said in Cal.com (was Calendso) - Calendly Alternative:
So I created a temporary database so long as you build this on a server with access to postgres this will work. The only problem is that I cannot figure out why it is stuck on localhost:3000 as opposed to accepting the new dns settings
Your work looks very promising! Unfortunately, there is not much feedback I can provide from the technical perspective.
-
@roofboard said in Cal.com (was Calendso) - Calendly Alternative:
I have made some progress here apparently calcom needs access to a database while running yarn build, and while running yarn it would be writing to /app/code
So I created a temporary database so long as you build this on a server with access to postgres this will work. The only problem is that I cannot figure out why it is stuck on localhost:3000 as opposed to accepting the new dns settings
https://git.draglabs.com/davidjstrom/cloudron-calcom-v2/-/tree/localhost-issue
@girish
Any thoughts?Thanks for working on this! Cal.com now works really well with Nextcloud calendar (I'm using the hosted service) so it'd be absolutely fantastic to have it on Cloudron!
Hopefully @staff can take a look at this package @roofboard has started and help get it finished up and into the app store!
-
Let's get this across the finish line! A decent scheduling alternative will be huge!
From what I can tell one of us just needs to:
- successfully complete a docker build (looks like @roofboard has made a start, well done
) - add the cloudron packaging files
I'm knew to this game, but it seems like we should then send a pull request to the main cal.com repo -- why not just stick with the primary repository on this one?
(
thanks to @jdaviescoates 's github issue, they've stated their friendly to having this available on cloudron)
- successfully complete a docker build (looks like @roofboard has made a start, well done
-
@roofboard re: "I cannot figure out why it is stuck on localhost:3000 as opposed to accepting the new dns settings" --
can you provide further details on the problem you've run into? Is this when you're just trying to get it to run on docker on your local machine? or when deploying as a custom cloudron app? I'm unclear what the status is.Some further elaboration might help us or @girish troubleshoot. If it's not cloudron specific, let's get a thread going with cal.com if we need to.
-
@tshirt-chihuahu thank you for being so enthusiastic about this one!
-
Referenced by
tshirt-chihuahu
-
Just a quick update from me....I did an initial test using cal.com (hosted by them) and their CalDAV integration with NextCloud, and it failed some of my required use case tests (recurring invites were buggy.....although it looks like one of the use cases may have been fixed already, so this means progress is being made....and I may need to re-test soon).
So this isn't quite high enough priority for me to mess with getting the deployment on Cloudron figured out since it can't quite solve my use case yet....
However, if you want this to progress, here's what I suggest:
- start using/testing a hosted cal.com account
- since you likely don't want to hand them your main login credentials, if you're using NextCloud, you can make a separate "scheduler" user, and then share that calendar with your main calendar. (NextCloud seems to have gotten much better at this.) Or...just make a test account and try it.
- post issues and talk back to the cal.com team.
The Cal team has a CalDAV integration issues roundup here you can check, comment on, prior to posting additional issues that you run into: https://github.com/calcom/cal.com/issues/3457 -
@tshirt-chihuahu yeah, I've been using the hosted version for a while now and I really like it!
For my use cases at least their integration with Nextcloud now works great after they ironed out various issues, so I'd love to be able to easily selfhost it on Cloudron as is!
-
-
I would be interested to know what priority the Cloudron team has for bringing Cal.com to Cloudron. To me it seems like a killer feature, and I don't quite understand why there has been so little input from them in this thread recently.
Is there a public app roadmap of some sort?
-
We actually wanted to package that already but mostly main bits of the app are not even public as far as I can tell. The main repo references git repos which are not available to the public: https://github.com/calcom/cal.com/tree/main/apps
-
@nebulon Interesting. I wasn't aware of that. Aren't all the necessary parts of the project public to deploy it on Cloudron? https://github.com/calcom/docker
-
@3699n I maybe misunderstand their repo structure, but as far as I can tell the backend is not open source, only the frontend assets are.
-
@nebulon I don't think that can be right. They certainly claim that it is fully self-hostable, it's deployable on Heroku, Railway, Vercel and Render, and I'm pretty sure I've seen people on Twitter saying they are self-hosting it.
In this Tweet by Cal.com back in July 2022 they claim over 10,000 people were already self-hosting:
https://twitter.com/calcom/status/1559246473853812736
And here is one of the founders and Co-CEOs saying people are self-hosting it:
https://twitter.com/peer_rich/status/1553123068289187840
And this one from 11 days ago saying they are putting in a lot of work to make self-hosting easier
https://twitter.com/peer_rich/status/1610967646652059650
Presumably you have already looked at that docker link?
https://github.com/calcom/docker
Perhaps ask for help/ clarification in their Slack? https://cal.com/slack
I've also just directly asked them on Twitter here and invited them to chime into this thread:
https://twitter.com/jdaviescoates/status/1615088837520228370
Edit:
Seems there are some issues with slowness when selfhosting though:
https://twitter.com/peer_rich/status/1610726994525945857
Also, I've now asked about this in their Slack too:
https://calendso.slack.com/archives/C01NXDSRY9W/p1673902893871239
-
As far as I understand, it can be selfhosted.
I've done it myself in the past (not being a developer) using an heroku instance.
-
@jdaviescoates Good initiative. If the community here can find the source, then I'm sure we can package it. Need some community help on the research and enlightenment though, as it's not been obvious to us.
-
@marcusquinn The source can be found at: https://github.com/calcom/cal.com/tree/e05bcf98c2348d2c322665fa752350134d7c74bb/apps/web
api,console, andwebsiteare not required for a Cal.com instance.api: Both REST API endpoints and tRPC resolvers
console: This is the admin console they use to manage their instance internally
website: Landing pagePlease see this issue for reference: https://github.com/calcom/cal.com/issues/1581
-
@nebulon Hey, I'm one of the founding engineers at Cal.com, @jdaviescoates invited me here to clarify on the open source state of our app. Cal.com is a COSS which means, it is commercialized open source software. So there are parts of the app that are not open source only for enterprise customers. But the backend and front end of the app are definitely all open source and that's why so many developers are able to contribute to the app. I hope this clarifies things for you.
-
Hey @alishahbaz many thanks for chiming in here
I have to say though, that hasn't really clarified much for me at all.
@alishahbaz said in Cal.com (was Calendso) - Calendly Alternative:
So there are parts of the app that are not open source only for enterprise customers.
I'm not exactly sure what you are saying here.
I think was you're saying is: that for enterprise customers only some parts are NOT open source.
Is that correct? If so, which parts?
Also, importantly, who counts as an enterprise customer?
Does this "some parts not open source" effect people who wish to self-host? (which is our concern here).
If so, which people, and under what circumstances?
@alishahbaz said in Cal.com (was Calendso) - Calendly Alternative:
But the backend and front end of the app are definitely all open source and that's why so many developers are able to contribute to the app
That's great, thanks.
But what we're looking for more clarity on here is not whether or not developers are able to contribute (although that is of course related - and of course it's also possible to contribute as a non developer, as I have already done so multiple times by reporting bugs and letting you debug bugs on my system): it is more whether or not users are able to self-host the complete stack, and if so, how exactly can they do that?
To be clear, I am only using and promoting Cal.com because I am under the impression that it is fully open source and self-hostable.
But I'm beginning to wonder if I should instead be publicly criticising it for "open washing" (I'm still reserving judgement on this - it sounds like it perhaps is currently possible to self-host the full stack for non-enterprise customers, but that at present that is rather complicated and not for the faint hearted - especially given very experienced developers like @nebulon can't work out how to do it)
Thank you in advance for any further clarification you can provide on the topics mentioned, to recount:
- Who counts as an "enterprise" customer?
- What is/ is not open source for such customers?
- Can enterprise/ non-enterprise customers self-host the full stack (even if parts of it are not open source for the enterprise customers, whoever they are)
- How exactly can they do that?
-
thanks for everyone chiming in here and @alishahbaz for the clarification. Generally we don't mind if open source or not, as long as we can build an app package. Seems like I got confused about the subrepo style there and somehow thought only pre-built docker images for the backend parts are delivered.
Anyways we will start looking into getting the app into the library soon.
-
@nebulon said in Cal.com (was Calendso) - Calendly Alternative:
Anyways we will start looking into getting the app into the library soon.
-
@jdaviescoates said in Cal.com (was Calendso) - Calendly Alternative:
I've also just directly asked them on Twitter here and invited them to chime into this thread:
https://twitter.com/jdaviescoates/status/1615088837520228370Just for completeness, here is the response I received:
-
@nebulon Amazing! Thank you!!
