calcom / cal.com Goto Github PK

Alongside Google & Office 365 calendar support maybe you could implement CalDav support as it's a nicely standardized, specified (RFC4791) and widely used protocol in stacks which try to rely on "Big Tech" as little as needed.

Hello!

This looks like a nice and promising project. I'm glad to have found out about it.

However, I'm more than a bit perplexed at the fact that yesterday (https://star-history.t9t.io/#calendso/calendso) it had 30 stars, and at the time I'm writing this (01:00 UTC Apr 16) there's 975 stars. About every 1 minute, when I reload the page, I see it has another star 🤔

Any reason for this?

Hi! very happy to discover this endeavour, try it out and post helpful bugs comments and suggestions.

In this case I notice that after you set up the slot format of the appointment type, then navigate to the public page to book an appointment it displays all slots as available, despite I have several already booked that would conflict.

In the case the app is not capable of fetching the events from the host calendar it should display some sort of error on the web interface and/or the server.

I'm on OSX Catalina. The app was installed and set up on localhost:3000.

Expected Behavior

1. Logout and redirect to login page, when user clicks on logout button

Current Behavior

on Chrome, with server currently on localhost.
username, name, email, password, bio are filled in DB. Besides startTime, endTime, createdDate,eventTypes and credentials.

Error Log

TypeError: Cannot read property 'user' of null
at getServerSideProps (webpack-internal:///./pages/settings/profile.tsx:429:22)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async renderToHTML (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/render.js:40:215)
at async /home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:109:97
at async /home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:102:142
at async DevServer.renderToHTMLWithComponents (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:134:387)
at async DevServer.renderToHTML (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:135:522)
at async DevServer.renderToHTML (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/server/next-dev-server.js:34:578)
at async DevServer.render (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:72:236)
at async Object.fn (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:56:580)
at async Router.execute (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/router.js:23:67)
at async DevServer.run (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:66:1042)
at async DevServer.handleRequest (/home/ritom/Desktop/Projects/calendso/node_modules/next/dist/next-server/server/next-server.js:34:504)

In order to be able to integrate with existing calendar software, ability to sync to a caldav server would be covering the majority of calendar integrations (including Google Calendar but also most on-prem solutions).

Email validation should be added to the the /book page email field. If an invalid email is given this later becomes an error whilst contacting the google calendar API. "There was an error contacting the Calendar service: Error: Invalid attendee email.". The call fails and the booking does not show up in the agent calendar.

Expected behaviour: Invalid email should become a client side validation error.

Please consider allowing mysql or postgresql

https://github.com/calendso/calendso/blob/f4dce81e5f2e32f063fcae93d1f44c9a98897a39/prisma/schema.prisma#L5

I think it's as simple as changing the data provider though

Hi guys,

great work with this first public version, off to a great start.

In my playing around with this I noticed odd behaviour with the start/end times: When setting start and end times to (for instance) 09:00-17:00 this results in guests being able to plan from 9:15 (or similar, depending on chosen event duration) till 17:00. Expected behaviour would be being able to plan from 9:00 till 16:45.

I think this should be a simple comparison bug somewhere (< vs <= or similar) but I'm still starting to find my way around this codebase, so I thought I'd report it here.

Recently, a new time zone feature was contributed 👏. Whilst this was a very welcome contribution, I think there are currently too many time zones — unnecessarily cluttering the code and the dropdown. I can see that the inspiration was drawn from here, but I'd make some changes to the options available. For example, at the moment, we have 13 different Argentinian cities, despite Argentina having one time zone...

We also have now three "Americas". US at the top, and then "America", which has both Latin American cities and ... Canadian cities, like Toronto. There is also inconsistency regarding time zone abbreviations - US ones have abbreviations of the time zones they are in, and the rest does not. Whilst I can appreciate why abbreviations could be high-maintenance as UK is in GMT but changes into BSM between March and October, it's either all or none, for the sake of consistency, imo.

Therefore, I'd refactor this by removing unnecessary entries, clean up the inconsistencies and ideally merge some options, as for example, Central European Time is used by the vast majority of European countries, with few exceptions, and yet every single country appears separately. Usually, for example, Dublin and London appear under the same option, since they are in the same time zone (with Ireland also switching into Irish Standard Time between March and October).

I am raising this as an issue, as I don't want to change things around myself as I wasn't the one implementing them — happy to discuss it further and change it myself if there are no volunteers.

congrats on product hunt achievement! i think it would be cool if you did a basic / simple self-hosted video tutorial on installing Calendso... perhaps using Laragon or something.

good luck!

Currently the default port for nextjs is 3000. If a process is currently using this port, yarn dev will not work.

This can be corrected with yarn dev -p 3030 but the callback etc. will fail when trying to login as it is expecting port 3000.

Hey, I followed the setup, created an entry using Prisma Studio, saved the record, but whenever I try to log in to the created user on http://localhost:3000/auth/login, it always tells me an "Incorrect Password" screen. I've copied and pasted the password, changed it a couple times, but still get the error

Mobile view (small widths)

Some buttons like Teams and Bookings are visible. And none of the tab links work, since I guess the hrefs are not specified.

Desktop view (larger widths)

Teams and Bookings tab buttons are invisible and links work, which is the intended behaviour I believe at the moment?

I personally think there isn't any reason why a 1 hour and 30 minute meeting should only be bookable every 1 hour and 30 minutes starting from 0:00. The system should be changed.

For example:
If my whole calendar is empty so there can't be colliding events, I'm still not able to book a 90 minute meeting at 14:00 even though it's logically possible.

The times shown there should be based on an API call to Google and therefore based on the real calendar. It's much more work to do but it just doesn't make any sense for the times to be generated based on event type length.

In order to make everything neater, we're asking that for all integration and feature requests, you use the Discussions tab.

An issue should be created once development starts on that integration or feature.

This way, we avoid having tons of issues for feature requests that aren't being developed yet.

I saw there is a field in the DB for the avatar, that should be a URL or some base64 for the image?

It would be amazing to have a plugin for WordPress

Maybe you could implement the option to switch from 12hr time format to 24hr time format. 24hr time format is used almost everywhere at least in Germany, the rest of Europe and I think also many other parts of the world.

Corresponding feature voting link

When running calendso on a port other than 3000, the console reports an issue with the auth API
https://next-auth.js.org/errors#client_fetch_error csrf FetchError: request to http://localhost:3000/api/auth/csrf failed, reason: connect ECONNREFUSED 127.0.0.1:3000 at ClientRequest.<anonymous> (C:\opt\calendso\node_modules\node-fetch\lib\index.js:1461:11) at ClientRequest.emit (events.js:223:5) at Socket.socketErrorListener (_http_client.js:406:9) at Socket.emit (events.js:223:5) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:81:21) { message: 'request to http://localhost:3000/api/auth/csrf failed, reason: connect ECONNREFUSED 127.0.0.1:3000', type: 'system', errno: 'ECONNREFUSED', code: 'ECONNREFUSED' }

I believe this is due to the code expecting the server to be on port 3000

There could be a fourth button for downloading a ics file for the scheduled meeting. iCalender is standardized by RFC, has pretty good documentation and is universally usable. For example when you open such a file in macOS it starts your Calendar app and gives you the possibility to add it to one of your calendars you have configured. (for example Google, Yahoo, Outlook, CalDav, iCloud, etc)

There are several NodeJS libraries for generating ics files. Download could be done using Data URLs.

Corresponding feature voting link

It would be nice if the user list could be provisioned from a connected LDAP instance. This would allow Admins to have a calendar link generated automatically when a new user is added, and also have the link automatically become invalid if the user gets deactivated/removed from LDAP.

Ideally one would be able to configure a LDAP filter string for the application to get a list of valid users.
The calendar link could simply be your.calendso.instance/the_username_from_ldap

_CAL-720

Within the pages/integrations.tsx page, the getIntegrations() function is called repeatedly, most likely due to the integration data using state, hence it is re-fetching the data constantly as the state refreshes.

Here's the problematic code:

const [integrations, setIntegrations] = useState([]);

function getIntegrations() {
        fetch('/api/integrations')
            .then((response) => response.json())
            .then((data) => setIntegrations(data));
}

// TODO: Stop this function from running repeatedly
getIntegrations()

Currently, there are a lot of SVG icons in the project. These all should be migrated to the Heroicons components, which look like this: <GlobeIcon />

Documentation for this can be found on the Heroicons GitHub repository

should be feasible by using https://nextjs.org/docs/advanced-features/i18n-routing

As a Calendso user who is invited to meet with the inviter, I want to share my availabilities via Calendso and let the inviter set the meeting duration/ending time, so that I don't need to ask the inviter for the meeting duration.

Hey, I wanted to give Calendso a shot and deploy it on my server.
I deploy everything with Docker, so I sketched simple Dockerfile.

I initialized DB and used BCrypt to encrypt my password.
However, upon login I am reaceiving "Incorrect password" error.

Here is a short screencast to demonstrate the whole process:
calendso_docker_incorrect_password.zip

I'm new to this project and I love it so much already.

Would be awesome to have a docker-compose file in order to start the environment (postgres and so on) and deploy it easily on a server.

Hey, I posted about this in the Slack channel but got no response

I managed to go through setup and add the Google Calendars integration and set busy times/make a new event type all on localhost, but nothing's changed for the website in general? I just see the following when I go to the Dashboard, Integration, and Availability pages

We need to add a section at the bottom of the calendar event descriptions allowing people to cancel and reschedule their meetings.

Like so:

Need to change this event?
Cancel: https://calendso.com/cancel/1289347189247
Reschedule: https://calendso.com/reschedule/1289347189247

It would be nice to add Stripe connect or simple copy/paste Stripe API keys and have an option to add price to the first step "Quick Chat $5" or "Demonstration $25" and add a credit card form (Stripe Element) before confirmation.

I'm new to Calendso. I'd be happy to work through the documentation but I see that docs.calendso.com is without an address. I'm guessing that means docs are not yet developed.

I was finally able to get Calendso installed on an Ubuntu instance. I'm having trouble creating a Calendso user. When I create one through Prisma Studio, the password that I enter is transformed to "null". I was hoping it's just getting hidden from display, but when I attempt to log in as that user, I get "Illegal arguments: string, object An error occurred when logging you in. Head back to the login screen and try again." I'm guessing that the object is "null" and it needs a password string.

Is there something special about the password field? Is it plaintext or a specially-formatted hash?

I get the following on the console after I select the date. It won't let me select time...it just keeps spinning.

TypeError: Cannot read property '0' of undefined
    at authorise (webpack-internal:///./pages/api/availability/[user].ts:32:88)
    at handler (webpack-internal:///./pages/api/availability/[user].ts:24:3)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async apiResolver (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/api-utils.js:8:1)
    at async DevServer.handleApiRequest (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:64:462)
    at async Object.fn (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:56:492)
    at async Router.execute (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/router.js:23:67)
    at async DevServer.run (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:66:1042)
    at async DevServer.handleRequest (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:34:504)
TypeError: Cannot read property '0' of undefined
    at authorise (webpack-internal:///./pages/api/availability/[user].ts:32:88)
    at handler (webpack-internal:///./pages/api/availability/[user].ts:24:3)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async apiResolver (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/api-utils.js:8:1)
    at async DevServer.handleApiRequest (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:64:462)
    at async Object.fn (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:56:492)
    at async Router.execute (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/router.js:23:67)
    at async DevServer.run (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:66:1042)
    at async DevServer.handleRequest (/home/testo101/test/calendso/node_modules/next/dist/next-server/server/next-server.js:34:504)

OS: Windowsfx (Ubuntu 20,04 LTS)
Node: v14.16.1
Yarn: 1.22.10

I see this project doesn't have any official releases, how should we know about changes or versions?

Am i missing documentation? Is https://docs.calendso.com/docs/ a draft?

Hey guys,

I have everything ready to add support for automatically generate a Google Meet link when creating an event. This is done on a per-event basis with a new column on the EventType table.

There are some nuances, but the main part is this, in the pages/api/book/[user].ts when creating the event:

{
  // ...
  conferenceData: {
    createRequest: {
      requestId: Math.random().toString(36).substring(7), // just generating any random string should do the trick
      conferenceSolutionKey: {
        type: "hangoutsMeet"
      },
    }
  }
}

If this is something you are interested in, I will do a PR.

If one wants to "Add a new event type", but then decides to cancel without actually adding a new event, a "Change your available times" pop-up is triggered.

The GIF below illustrates the unintended behaviour.

Bit of an accidental find; When booking a slot, if the slot being booked > the length of an existing event E.g. I have an event in my calendar from 9:15 until 9:30, this is properly blocked from booking in 15 minute booking slot times, but if I by chance have 1-hour event types as well, I am still able to book 9:00-10:00. This is due to the code checking whether the slot you are booking time is between the start and end busyTime, but not whether the slot you are booking overlaps with a smaller, other event.

First of all, thanks for open sourcing this project! Congrats on the launch, the product looks really great and I'm excited to use it!

There's an issue with the alignment of the days on the calendar when I take a look at the demo (https://app.calendso.com/bailey/1). It looks like the first day of the month starts in the top left of the month view, regardless of which day of the week the first day of the month actually is. That causes all the following days to be misaligned, so clicking on the 23rd of April for example is a Friday, but it's spatially in the column that would typically be a Monday on most calendars.

This is summed up in a comment on hacker News (https://news.ycombinator.com/item?id=26818957):

Also, what an odd calendar layout. Starting with the first day of the month at the top left means all the days are off for most months. Why would Thursday be at the very left side (as is the case in April)?? (I was initially trying to find out if the layout was Sunday or Monday starting, but apparently it's neither)

I will be starting working on Kubernetes Support. Adding this issue so everbody can follow up here.

Currently Calendso exposes a way for anyone to book a slot in your calendar. For my use-case, I would like to be able to create a one-time use link that I can send to someone and have them book a slot via. Essentially to just to be able to generate a token with an expiry, and then to have the application verify that the token is still valid before accepting the booking.

Add the ability to create event types that do not show on the /user page, and instead can only be accessed by going to /user/type

Often when people book an event, because the booking API call isn’t that fast, they press it twice. And if they press the button twice, it books it twice.

Need to add a loading state for when the button has been pressed, so it displays a spinner in the button or something and disables the button while it loads.

Suggestion: Please add support to Redis for all reads and write, update delete should be done on PostgreSQL as well Redis, so Redis will remain always updated.
Thank you

Hello and first things first, thanks for this!

I'm a heavy user of calendly and one things I love so much are availability schedules.
I think is a must have with calendso as well. Pretty happy to help testing or brainstorming it, and adopting it in my company!

Guess the title should be self explainatory. 2FA via TOTP is a open standard which should normally be relatively easy to implement and is getting more important in this modern and connected time.

Corresponding feature voting in GitHub discussions: #72

Currently it looks like the calendar is hard-coded to Europe/London. This should likely be set to the timezone of the calendar, or perhaps a setting on the user.

Not sure what the experience from the user perspective is - if it should show in the timezone of the calendar or if it should be translated into the timezone of the user.

This is an issue to track zoom integration (a zoom link should be generated for the meeting automatically).

I offer "office hours" to my Github sponsors, and would love to use Calendso for booking. One necessarily feature for this use-case, that Calendly does not offer in its free tier, is to check availability across multiple calendars.

That is, I have a work calendar and a personal calendar. I want to book the event in my personal calendar, but I want to make sure that there isn't already something booked in either my personal or my work calendar.