Cal.com (was Calendso) - Calendly Alternative
-
2.8 is out:
Not only that, but there is now also a $100 bounty on packaging it for Cloudron!
https://github.com/calcom/cal.com/issues/3026#issuecomment-1509352147
-
@jdaviescoates
get that bounty up to 1000 and I will spend another week on it and it will be done. -- Already half way there. -
@roofboard it's nothing to do with me
-
Looks like there's a Pull Request related to the bounty on this:
Give it your emoji support
-
-
Seems they are generally supportive of it being on Cloudron, in at least making it compatible, I think the rest is our side of the packaging job.
-
While these two relevant issues (https://github.com/calcom/cal.com/issues/3026 and https://github.com/calcom/cal.com/issues/6780) remain open, it looks like a PR was merged and released in 2.9.5 a few weeks ago that addressed both of these: "feat: Make database optional when building" (https://github.com/calcom/cal.com/pull/8561)
-
Honestly, not having this and the lack of new apps for businesses was the reason I didn't renew my subscription. Cloudron is definitely the easiest solution to work with, but for $150 a year I anticipated more apps being released over the past year.
-
@ajtatum There's no lack of willing to package apps, the issues more come from the apps themselves having difficulties in working with a locked-down Docker setup, and the author's don't have to make their apps compatible if they prefer to use unusual stack setups.
Sure you can package them in vanilla Docker, but then you have all the maintenance and debugging that app store managed apps have done for you.
FWIW, if you didn't already look, Easy Appointments is already available:
And these are free Wordpress plugins options:
Cal.com does look great, and I've seen the 95% of work done on it to attempt to make is Cloudron-easy as an app store app, but sometimes that last 5% is many times more work, and then author negotiation, than the 95% part.
I guess that's the thing about open-source, no-one is entitled to anything, it's always going to be a best effort at the time offering.
If you want guarantees, then you can always subscribe to cal.com directly, and influence their development directly.
I think the expectation that Cloudron fixes every apps inadequacies to package and maintain and make easy for all, is always going to need some pragmatism.
As they say, you can pay with your money, or with your time, at least you have that freedom of choice and voice here.
-
@sparkwise Doesn't the PR you linked resolve the issues that have previously been blocking the packaging as a Cloudron app? Would it be possible for you to take another look @girish ? Cal.com would still be a killer app to have on the platform.
-
-
@girish said in Cal.com (was Calendso) - Calendly Alternative:
@3699n yes, I think it's worthwhile re-investigating the current situation with selfhosting cal.com . Added to our internal list.
FYI, I am as of yesterday attempting to package cal.com for Cloudron, so far, the project dependencies installation and building is working. I am currently looking over the startup part of cal.com, and might be able to provide a working package or, at the least, a good starting point.
-
The code of my attempt at packaging cal.com for Cloudron is here
The package works as in:
- Installation of node_modules works
- Building works
- Supposedly - I have not tested this part, thus why I'm handing my code out here - the start script should work correctly
- Required environment vars are configured during first startup of the application and verified at each start
@girish The repo code that I linked can be freely used as a good advanced starting point by the team in order to package cal.com. If there are any questions, please feel free to ask by mentioning me in this thread
-
We have a package at https://git.cloudron.io/cloudron/calcom-app which @vladimir-d polished to some degree. It mostly works, however it requires patching code for the domain, which cal.com so far requires at build time.
Currently, the plan is to wait for few more releases and see if this current patching approach is solid enough to publish the package then.
-
