Typos in docs (#7898)
This commit is contained in:
@ -11,7 +11,7 @@ This document is maintained by the community. It might contain issues.
|
||||
|
||||
## Kubernetes via Terraform and Manifests
|
||||
|
||||
Community-led documentation for Kubernetes deployment is available (here)[https://github.com/twentyhq/twenty/tree/main/packages/twenty-docker/k8s]
|
||||
Community-led documentation for Kubernetes deployment is available [here](https://github.com/twentyhq/twenty/tree/main/packages/twenty-docker/k8s)
|
||||
|
||||
## Render
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ yarn command:prod cron:calendar:calendar-event-list-fetch
|
||||
['REFRESH_TOKEN_COOL_DOWN', '1m', 'Refresh token cooldown'],
|
||||
['FILE_TOKEN_SECRET', '<random>', 'Secret used for the file tokens'],
|
||||
['FILE_TOKEN_EXPIRES_IN', '1d', 'File token expiration time'],
|
||||
['API_TOKEN_EXPIRES_IN', '1000y', 'Api token expiration time'],
|
||||
['API_TOKEN_EXPIRES_IN', '1000y', 'API token expiration time'],
|
||||
]}></ArticleTable>
|
||||
|
||||
### Auth
|
||||
@ -91,10 +91,10 @@ yarn command:prod cron:calendar:calendar-event-list-fetch
|
||||
['EMAIL_FROM_NAME', 'John from YourDomain', 'Global name From: header used to send emails'],
|
||||
['EMAIL_SYSTEM_ADDRESS', 'system@yourdomain.com', 'Email address used as a destination to send internal system notification'],
|
||||
['EMAIL_DRIVER', 'logger', "Email driver: 'logger' (to log emails in console) or 'smtp'"],
|
||||
['EMAIL_SMTP_HOST', '', 'Email Smtp Host'],
|
||||
['EMAIL_SMTP_PORT', '', 'Email Smtp Port'],
|
||||
['EMAIL_SMTP_USER', '', 'Email Smtp User'],
|
||||
['EMAIL_SMTP_PASSWORD', '', 'Email Smtp Password'],
|
||||
['EMAIL_SMTP_HOST', '', 'Email SMTP Host'],
|
||||
['EMAIL_SMTP_PORT', '', 'Email SMTP Port'],
|
||||
['EMAIL_SMTP_USER', '', 'Email SMTP User'],
|
||||
['EMAIL_SMTP_PASSWORD', '', 'Email SMTP Password'],
|
||||
]}></ArticleTable>
|
||||
|
||||
#### Email SMTP Server configuration examples
|
||||
@ -143,7 +143,7 @@ yarn command:prod cron:calendar:calendar-event-list-fetch
|
||||
['STORAGE_S3_ENDPOINT', '', 'Use if a different Endpoint is needed (for example Google)'],
|
||||
['STORAGE_S3_ACCESS_KEY_ID', '', 'Optional depending on the authentication method'],
|
||||
['STORAGE_S3_SECRET_ACCESS_KEY', '', 'Optional depending on the authentication method'],
|
||||
['STORAGE_LOCAL_PATH', '.local-storage', 'data path (local storage)'],
|
||||
['STORAGE_LOCAL_PATH', '.local-storage', 'Data path (local storage)'],
|
||||
]}></ArticleTable>
|
||||
|
||||
### Custom Code Execution
|
||||
@ -201,7 +201,7 @@ This feature is WIP and is not yet useful for most users.
|
||||
|
||||
<ArticleTable options={[
|
||||
['SUPPORT_DRIVER', 'front', "Support driver ('front' or 'none')"],
|
||||
['SUPPORT_FRONT_HMAC_KEY', '<secret>', 'Suport chat key'],
|
||||
['SUPPORT_FRONT_HMAC_KEY', '<secret>', 'Support chat key'],
|
||||
['SUPPORT_FRONT_CHAT_ID', '<id>', 'Support chat id'],
|
||||
]}></ArticleTable>
|
||||
|
||||
|
||||
@ -84,7 +84,7 @@ yarn command:prod upgrade-0.30
|
||||
```
|
||||
|
||||
The `yarn database:migrate:prod` command will apply the migrations to the database structure (core and metadata schemas)
|
||||
The `yarn command:prod upgrade-30` takes care of the data migration of all workspaces.
|
||||
The `yarn command:prod upgrade-0.30` takes care of the data migration of all workspaces.
|
||||
|
||||
# v0.30.0 to v0.31.0
|
||||
|
||||
@ -97,7 +97,7 @@ yarn command:prod upgrade-0.31
|
||||
```
|
||||
|
||||
The `yarn database:migrate:prod` command will apply the migrations to the database structure (core and metadata schemas)
|
||||
The `yarn command:prod upgrade-31` takes care of the data migration of all workspaces.
|
||||
The `yarn command:prod upgrade-0.31` takes care of the data migration of all workspaces.
|
||||
|
||||
# v0.31.0 to v0.32.0
|
||||
|
||||
|
||||
@ -72,7 +72,7 @@ Here's how you can do it:
|
||||
|
||||
2. To the right of the line, three vertically aligned dots symbolize a menu button. Click on this to unveil a dropdown list of options.
|
||||
|
||||
3. In the dropdown menu, find and click on the "deactivate" option.
|
||||
3. In the dropdown menu, find and click on the "Deactivate" option.
|
||||
|
||||
<img src="/images/user-guide/fields/deactivate-field.png" style={{width:'100%'}}/>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user