Our self-hosted instance of cal.com https://cal.pub0.org
 
 
 
 
 
Go to file
Bailey Pumfleet 3a6eae8b8f Update dashboard 2021-05-11 14:11:17 +01:00
.github/ISSUE_TEMPLATE Create issue templates 2021-04-28 14:10:55 +01:00
components Update dashboard 2021-05-11 14:11:17 +01:00
lib Implemented configurable eventType phone or physical locations. 2021-05-08 19:03:47 +00:00
pages Update dashboard 2021-05-11 14:11:17 +01:00
prisma Implemented configurable eventType phone or physical locations. 2021-05-08 19:03:47 +00:00
public fixed logo 2021-05-07 19:23:00 +01:00
styles Add booking flow 2021-03-22 13:48:48 +00:00
.env.example Added telemetry collection (through jitsu.com) 2021-04-27 17:19:12 +03:00
.gitignore Add booking flow 2021-03-22 13:48:48 +00:00
LICENSE Add booking flow 2021-03-22 13:48:48 +00:00
README.md Update README.md 2021-05-08 20:46:37 +01:00
calendso.yaml Add OpenAPI Specification 2021-04-16 14:16:01 +01:00
next-env.d.ts Add booking flow 2021-03-22 13:48:48 +00:00
next.config.js Added redirects() function to next.config.js, changed Settings url 2021-05-07 15:04:56 +00:00
package.json Merge pull request #176 from emrysal/feature/implement-phone-and-physical-locations 2021-05-08 20:49:04 +01:00
postcss.config.js Add booking flow 2021-03-22 13:48:48 +00:00
tailwind.config.js fix calendar style and resolve some TS lint errors 2021-05-04 20:42:01 -07:00
tsconfig.json Add booking flow 2021-03-22 13:48:48 +00:00
yarn.lock Merge pull request #176 from emrysal/feature/implement-phone-and-physical-locations 2021-05-08 20:49:04 +01:00

README.md

Logo

Calendso

The open-source Calendly alternative.
Learn more »

Slack · Website · Issues

About The Project

Calendso Screenshot

Let's face it: 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.

Product of the Month: April

Support us on Product Hunt

Calendso - The open source Calendly alternative | Product Hunt

Built With

Stay Up-to-Date

Calendso is currently in alpha. Watch releases of this repository to be notified for future updates:

calendso-star-github

Getting Started

To get a local copy up and running, please follow these simple steps.

Prerequisites

Here is what you need to be able to run Calendso.

  • Node.js
  • PostgreSQL
  • Yarn (recommended)

You will also need Google API credentials. You can get this from the Google API Console. More details on this can be found below under the Obtaining the Google API Credentials section.

Development Setup

  1. Clone the repo

    git clone https://github.com/calendso/calendso.git
    
  2. Install packages with yarn

    yarn install
    
  3. Copy .env.example to .env

  4. Configure environment variables in the .env file. Replace <user>, <pass>, <db-host>, <db-port> with their applicable values

    DATABASE_URL='postgresql://<user>:<pass>@<db-host>:<db-port>'
    GOOGLE_API_CREDENTIALS='secret'
    
    If you don't know how to configure the DATABASE_URL, then follow the steps here
    1. Create a free account with Heroku.

    2. Create a new app. Google Chrome — CleanShotX | 2021-04-20 at 02 01 56

    3. In your new app, go to Overview and next to Installed add-ons, click Configure Add-ons. We need this to set up our database. image

    4. Once you clicked on Configure Add-ons, click on Find more add-ons and search for postgres. One of the options will be Heroku Postgres - click on that option. image

    5. Once the pop-up appears, click Submit Order Form - plan name should be Hobby Dev - Free. Google Chrome — CleanShotX | 2021-04-20 at 02 04 29

    6. Once you completed the above steps, click on your newly created Heroku Postgres and go to its Settings. image

    7. In Settings, copy your URI to your Calendso .env file and replace the postgresql://<user>:<pass>@<db-host>:<db-port> with it. image image

    8. To view your DB, once you add new data in Prisma, you can use Heroku Data Explorer.

  5. Set up the database using the Prisma schema (found in prisma/schema.prisma)

    npx prisma db push --preview-feature
    
  6. Run (in development mode)

    yarn dev
    
  7. Open Prisma Studio to look at or modify the database content:

    npx prisma studio
    
  8. Click on the User model to add a new user record.

  9. Fill out the fields (remembering to encrypt your password with BCrypt) and click Save 1 Record to create your first user.

  10. Open a browser to http://localhost:3000 and login with your just created, first user.

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

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.

  1. Fork the project
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Make your changes
  4. Commit your changes (git commit -m 'Add some AmazingFeature')
  5. Push to the branch (git push origin feature/AmazingFeature)
  6. Open a pull request

Obtaining the Google API Credentials

  1. 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.
  2. In the search box, type calendar and select the Google Calendar API search result.
  3. Enable the selected API.
  4. 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.
  5. In the second page on Scopes, select Add or Remove Scopes. Search for Calendar.event and select the scope with scope value .../auth/calendar.events and select Update.
  6. 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.
  7. Now select Credentials from the side pane and then select Create Credentials. Select the OAuth Client ID option.
  8. Select Web Application as the Application Type.
  9. Under Authorized redirect URI's, select Add URI and then add the URI <CALENDSO URL>/api/integrations/googlecalendar/callback replacing CALENDSO URL with the URI at which your application runs.
  10. 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.
  11. 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

  1. Open Azure App Registration and select New registration
  2. Name your application
  3. Set Who can use this application or access this API? to Accounts in any organizational directory (Any Azure AD directory - Multitenant)
  4. Set the Web redirect URI to <CALENDSO URL>/api/integrations/office365calendar/callback replacing CALENDSO URL with the URI at which your application runs.
  5. Use Application (client) ID as the MS_GRAPH_CLIENT_ID attribute value in .env
  6. Click Certificates & secrets create a new client secret and use the value as the MS_GRAPH_CLIENT_SECRET attriubte

License

Distributed under the MIT License. See LICENSE for more information.

Acknowledgements

Special thanks to these amazing projects which help power Calendso: