Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Add language to code blocks.

This commit is contained in:
Alex Vandiver 2023-05-30 23:18:00 +00:00 committed by Tim Abbott
parent adb30c4d18
commit 9a6529f86a
4 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/production/authentication-methods.md
View File

@ -330,7 +330,7 @@ settings in `/etc/zulip/settings.py`.
An example configation for Active Directory group restriction can be: An example configation for Active Directory group restriction can be:
``` ```python
import django_auth_ldap import django_auth_ldap
AUTH_LDAP_GROUP_TYPE = django_auth_ldap.config.ActiveDirectoryGroupType() AUTH_LDAP_GROUP_TYPE = django_auth_ldap.config.ActiveDirectoryGroupType()
@ -613,7 +613,7 @@ integration](../production/scim.md).
Save the certificate in a new `{idp_name}.crt` file constructed as follows: Save the certificate in a new `{idp_name}.crt` file constructed as follows:
``` ```text
-----BEGIN CERTIFICATE----- -----BEGIN CERTIFICATE-----
{Paste the content here} {Paste the content here}
-----END CERTIFICATE----- -----END CERTIFICATE-----
@ -676,7 +676,7 @@ this with another IdP.
`/etc/zulip/settings.py` as `slo_url`. For example it may look like `/etc/zulip/settings.py` as `slo_url`. For example it may look like
this: this:
``` ```text
"your_keycloak_idp_name": { "your_keycloak_idp_name": {
"entity_id": "https://keycloak.example.com/auth/realms/yourrealm", "entity_id": "https://keycloak.example.com/auth/realms/yourrealm",
"url": "https://keycloak.example.com/auth/realms/yourrealm/protocol/saml", "url": "https://keycloak.example.com/auth/realms/yourrealm/protocol/saml",

2
docs/production/deployment.md
View File

@ -511,7 +511,7 @@ Apache requires you use the hostname, not the IP address; see
1. Enable some required Apache modules: 1. Enable some required Apache modules:
``` ```bash
a2enmod ssl proxy proxy_http headers rewrite a2enmod ssl proxy proxy_http headers rewrite
``` ```

2
docs/production/email-gateway.md
View File

@ -122,7 +122,7 @@ Congratulations! The integration should be fully operational.
1. Test your configuration by sending emails to the target email 1. Test your configuration by sending emails to the target email
account and then running the Zulip tool to poll that inbox: account and then running the Zulip tool to poll that inbox:
``` ```bash
su zulip -c '/home/zulip/deployments/current/manage.py email_mirror' su zulip -c '/home/zulip/deployments/current/manage.py email_mirror'
``` ```

6
docs/production/scim.md
View File

@ -23,13 +23,13 @@ The Zulip server-side configuration is straightforward:
example, if your organization is hosted on a subdomain example, if your organization is hosted on a subdomain
(`subdomain.zulip.example.com`): (`subdomain.zulip.example.com`):
``` ```bash
/home/zulip/deployments/current/manage.py add_scim_client okta -r 'subdomain' /home/zulip/deployments/current/manage.py add_scim_client okta -r 'subdomain'
``` ```
Or your organization is hosted on the root domain (`zulip.example.com`): Or your organization is hosted on the root domain (`zulip.example.com`):
``` ```bash
/home/zulip/deployments/current/manage.py add_scim_client okta -r "" /home/zulip/deployments/current/manage.py add_scim_client okta -r ""
``` ```
@ -39,7 +39,7 @@ The Zulip server-side configuration is straightforward:
1. Configure the Zulip server by adding a `SCIM_CONFIG` block to your 1. Configure the Zulip server by adding a `SCIM_CONFIG` block to your
`/etc/zulip/settings.py`: `/etc/zulip/settings.py`:
``` ```python
SCIM_CONFIG = { SCIM_CONFIG = {
"subdomain": { "subdomain": {
"bearer_token": "<secret token>", "bearer_token": "<secret token>",