Calendly and other scheduling tools are awesome. It made our lives massively easier. We're using it for business meetings, seminars, yoga classes and even calls with our families. However, most tools are very limited in terms of control and customisations. That's where Calendso comes in. Self-hosted or hosted by us. White-label by design. API-driven and ready to be deployed on your own domain. Full control of your events and data. Calendso is to Calendly what GitLab is to GitHub.
Calendso is currently in alpha. Watch releases of this repository to be notified for future updates:
To get a local copy up and running, please follow these simple steps.
Here is what you need to be able to run Calendso.
- Yarn (recommended)
Clone the repo
git clone https://github.com/calendso/calendso.git
Install packages with yarn
Configure environment variables in the .env file. Replace
<db-port>with their applicable values
If you don't know how to configure the DATABASE_URL, then follow the steps here
Set up the database using the Prisma schema (found in
npx prisma db push --preview-feature
Run (in development mode)
Open Prisma Studio to look at or modify the database content:
npx prisma studio
Click on the
Usermodel to add a new user record.
Fill out the fields (remembering to encrypt your password with BCrypt) and click
Save 1 Recordto create your first user.
Open a browser to http://localhost:3000 and login with your just created, first user.
Upgrading from earlier versions
Pull the current version:
Apply database migrations by running one of the following commands:
In a development environment, run:
npx prisma migrate dev
(this can clear your development database in some cases)
In a production environment, run:
npx prisma migrate deploy
.env.exampleand compare it to your current
.envfile. In case there are any fields not present in your current
.env, add them there.
For the current version, especially check if the variable
BASE_URLis present and properly set in your environment, for example:
Start the server. In a development environment, just do:
For a production build, run for example:
yarn build yarn start
Enjoy the new version.
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the project
- Create your feature branch (
git checkout -b feature/AmazingFeature)
- Make your changes
- Commit your changes (
git commit -m 'Add some AmazingFeature')
- Push to the branch (
git push origin feature/AmazingFeature)
- Open a pull request
Obtaining the Google API Credentials
- Open Google API Console. If you don't have a project in your Google Cloud subscription, you'll need to create one before proceeding further. Under Dashboard pane, select Enable APIS and Services.
- In the search box, type calendar and select the Google Calendar API search result.
- Enable the selected API.
- Next, go to the OAuth consent screen from the side pane. Select the app type (Internal or External) and enter the basic app details on the first page.
- In the second page on Scopes, select Add or Remove Scopes. Search for Calendar.event and select the scope with scope value
.../auth/calendarand select Update.
- In the third page (Test Users), add the Google account(s) you'll using. Make sure the details are correct on the last page of the wizard and your consent screen will be configured.
- Now select Credentials from the side pane and then select Create Credentials. Select the OAuth Client ID option.
- Select Web Application as the Application Type.
- Under Authorized redirect URI's, select Add URI and then add the URI
<CALENDSO URL>/api/integrations/googlecalendar/callbackreplacing CALENDSO URL with the URI at which your application runs.
- The key will be created and you will be redirected back to the Credentials page. Select the newly generated client ID under OAuth 2.0 Client IDs.
- Select Download JSON. Copy the contents of this file and paste the entire JSON string in the .env file as the value for GOOGLE_API_CREDENTIALS key.
Obtaining Microsoft Graph Client ID and Secret
- Open Azure App Registration and select New registration
- Name your application
- Set Who can use this application or access this API? to Accounts in any organizational directory (Any Azure AD directory - Multitenant)
- Set the Web redirect URI to
<CALENDSO URL>/api/integrations/office365calendar/callbackreplacing CALENDSO URL with the URI at which your application runs.
- Use Application (client) ID as the MS_GRAPH_CLIENT_ID attribute value in .env
- Click Certificates & secrets create a new client secret and use the value as the MS_GRAPH_CLIENT_SECRET attriubte
Obtaining Zoom Client ID and Secret
- Open Zoom Marketplace and sign in with your Zoom account.
- On the upper right, click "Develop" => "Build App".
- On "OAuth", select "Create".
- Name your App.
- Choose "Account-level app" as the app type.
- De-select the option to publish the app on the Zoom App Marketplace.
- Click "Create".
- Now copy the Client ID and Client Secret to your .env file into the
- Set the Redirect URL for OAuth
<CALENDSO URL>/api/integrations/zoomvideo/callbackreplacing CALENDSO URL with the URI at which your application runs.
- Also add the redirect URL given above as a whitelist URL and enable "Subdomain check". Make sure, it says "saved" below the form.
- You don't need to provide basic information about your app. Instead click at "Scopes" and then at "+ Add Scopes". Search for and check the following scopes:
1. account:master 2. account:read:admin 3. account:write:admin 4. meeting:master 5. meeting:read:admin 6. meeting:write:admin 7. user:master 8. user:read:admin 9. user:write:admin
- Click "Done".
- You're good to go. Now you can easily add your Zoom integration in the Calendso settings.