c5444c84fc
* Initial commit Created from https://vercel.com/new * Update config * Homepage * Self-hosting * Integrations * More docs pages * Developer docs * Update billing.mdx * Update install.mdx * Fix install guide * More fixes * Adding CSS guide * Fix capitalisation on Microsoft page * Added delete account update * Added Zapier integration question * Added GMeet integration part * Added Delete Account to Settings * unnecessary question mark * Added a link to Settings * Added stuff in Billing * Added a link to cal.com/signup * Capitalization * Added language change * Added more stuff in Event Types * Added how to change email * Added FAQ page * Spelling mistake * Added a title to FAQ * Added more stuff to Billing * Availability multi-booking * Deleted from Availability added to FAQ * Added to FAQ * Removed the dot * Added stuff to FAQ * Add license warning to adding CSS page * Update docker.mdx * Add import instructions * removed readme until we have our own * updated favicon, added cal sans * added new cal sans * Create README.md * renamed all github links * renamed more github links * Added team's Event Types * Clarified the Google Meet integration * Spelling error * Added primary calendar tutorial * Removed tutorial * primary calendar selection * Moved to subdirectory * Matching configs * Shares eslint config between web and docs * Removes format-schemas * Updates env file location in turbo * [docs] updates monorepo intructions Co-authored-by: baileypumfleet <pumfleet@hey.com> Co-authored-by: Peer Richelsen <peeroke@gmail.com> Co-authored-by: milospuac <97884287+milospuac@users.noreply.github.com> Co-authored-by: Peer Richelsen <peeroke@richelsen.net>
43 lines
No EOL
1,019 B
Text
43 lines
No EOL
1,019 B
Text
# Upgrading
|
|
|
|
**Warning**: When performing database migrations, you may lose data if the migration is not done properly.
|
|
|
|
1. Pull the current version:
|
|
```
|
|
git pull
|
|
```
|
|
2. Apply database migrations by running <b>one of</b> 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
|
|
```
|
|
|
|
3. Check the `.env.example` and compare it to your current `.env` file. 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_URL` is present and properly set in your environment, for example:
|
|
|
|
```
|
|
BASE_URL='https://yourdomain.com'
|
|
```
|
|
|
|
4. Start the server. In a development environment, just do:
|
|
```
|
|
yarn dev
|
|
```
|
|
For a production build, run for example:
|
|
```
|
|
yarn build
|
|
yarn start
|
|
```
|
|
5. Enjoy the new version. |