top | item 34508935

(no title)

deforciant | 3 years ago

the problem with cal.com "open source" self-hosting is that they have made it quite difficult to run yourself. For example this https://developer.cal.com/self-hosting/docker actually doesn't provide docker images but you need to build it yourself because for some reason frontend needs hardcoded hostname. In no other app I have seen such limitations :) Also, an older version from a year ago just stopped working, couldn't fix it, couldn't update it either :D

It would be good if someone made a fork with fixed setup and docker images for self-hosting :)

discuss

order

saddist0|3 years ago

Why does it need to be a fork and not contribution to this repo?

There is no end of feature requests, but polite way is to appreciate what is already done by original authors and fill your requests as GitHub issue.

Disclaimer: not affiliated to them, just find your comment disrespectful.

candiddevmike|3 years ago

One reason would be a CLA. Presumably to contribute to their main repo, you need to sign a CLA to ensure they can relicense this thing as needed. A separate fork wouldn't have that requirement, or shouldn't if it's in good faith.

deforciant|3 years ago

Didn't want to sound disrespectful, I did like the UI and liked the idea of self-hosting. Regarding fork vs pr - just putting myself into their shoes I understand why there's probably no will to make the self-hosting easy and potentially make it a bit harder than it should be :)

nxmnxm99|3 years ago

Judging by their English they’re almost certainly from the Baltic so I don’t think his tone was intended as disrespectful

junon|3 years ago

This puzzles me, there are often cases where hostnames are baked into frontends. Also, not everyone wants to use docker, so it's not exactly mandatory to have docker images. Dockerizing most things is rather simple, anyway.

gumby|3 years ago

I prefer to simply install rather than use docker.