Cal.com (was Calendso) - Calendly Alternative
-
The latest comment I see is that they don't plan to support Cloudron, but they open to merge it in, if someone will do the job of integrating, unfortunately.
@potemkin_ai yeah, hoping they'd package it for us was a bit hopeful, but still worth putting it out there imho
Hopefully someone else will take a look.
-
@fbartels I'm about to give up, just checked where cal.com wants to write during the yarn process and there are many many folders. The Dockerfile their community provides is also no help, since the URL needs to be supplied during build, which doesn't work in Cloudrons case. So yea, the current status is pretty useless to improve from
-
@msbt
Hi, I would like to take a look at this. I recently built my own N8N instance. And would really like to get cal.com running on cloudron.Could you share more of your work in progress?
@roofboard Ohhh... I like your n8n changes! I have a couple questions if you don't mind. I'll send you message.
-
-
@thetomester13 What is the connection between Calendso and Cal.com? Is Calendso just a community edition / Free Software version of Cal.com?
@LoudLemur no, cal.com is the new name for calendso
-
@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
-
@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.
-
@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 great news, thanks! Hopefully @staff or @appdev can help out too!
-
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? -
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.
-
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:
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
-
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 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.
-
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)
@tshirt-chihuahu thank you for being so enthusiastic about this one!
- successfully complete a docker build (looks like @roofboard has made a start, well done
-
T tshirt-chihuahu referenced this topic on
-
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
