Go to file
2021-12-17 10:46:58 -05:00
.github/workflows commit initial docker build/push workflow 2021-12-17 10:46:58 -05:00
calendso@c0c4cb53db Auto updated submodule references 2021-12-17 04:20:30 +00:00
scripts Make use of internal docker networks unifi database name 2021-12-15 16:01:30 +01:00
.env.example Make use of internal docker networks unifi database name 2021-12-15 16:01:30 +01:00
.gitignore rename .env to .env.example to match calendso repo pattern 2021-10-27 13:08:30 -04:00
.gitmodules Updated .gitmodules to use https & update Calendso submodule every 4 hours 2021-08-16 20:01:23 +00:00
docker-compose.yaml Make use of internal docker networks unifi database name 2021-12-15 16:01:30 +01:00
Dockerfile add build args and temporarily remove alpine 2021-11-19 10:57:57 -05:00
LICENSE Updated license to MIT to copy main repo 2021-07-02 22:09:43 +01:00
README.md add remark about SSL termination 2021-11-19 11:21:32 -05:00

calendso-docker

The Docker configuration for Calendso is an effort powered by people within the community. Calendso does not provide official support for Docker, but we will accept fixes and documentation. Use at your own risk.

Requirements

Make sure you have docker & docker-compose installed on the server / system.

Getting Started

  1. Clone calendso-docker

    git clone --recursive https://github.com/calendso/docker.git calendso-docker
    
  2. Change into the directory

    cd calendso-docker
    
  3. Rename .env.example to .env and update .env if needed.

  4. Build and start calendso

    docker-compose up --build
    
  5. Start prisma studio

    docker-compose exec calendso npx prisma studio
    
  6. Open a browser to http://localhost:5555 to look at or modify the database content.

  7. Click on the User model to add a new user record.

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

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

Git Submodules

This repository uses a git submodule.

If you cloned the repository without using --recursive, then you can initialize and clone the submodule with the following steps.

  1. Init the submodule

    git submodule init
    
  2. Update the submodule

    git submodule update --remote
    

For more advanced usage, please refer to the git documentation: https://git-scm.com/book/en/v2/Git-Tools-Submodules

Troubleshooting

  • SSL edge termination: If running behind a load balancer which handles SSL certificates, you will need to add the environmental variable NODE_TLS_REJECT_UNAUTHORIZED=0 to prevent requests from being rejected. Only do this if you know what you are doing and trust the services/load-balancers directing traffic to your service.