paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-01 12:33:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fix missing references.

Browse Source
This commit is contained in:
Alex Vandiver
2025-01-21 21:21:41 +00:00
committed by Tim Abbott
parent dbced00e47
commit d74e176cbe
5 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/development/setup-recommended.md
View File

@@ -1222,7 +1222,6 @@ remove the `GUEST_CPUS` and `GUEST_MEMORY_MB` lines from
[vagrant-dl]: https://www.vagrantup.com/downloads.html [vagrant-dl]: https://www.vagrantup.com/downloads.html
[install-advanced]: setup-advanced.md [install-advanced]: setup-advanced.md
[remote-wsl]: https://code.visualstudio.com/docs/remote/wsl-tutorial [remote-wsl]: https://code.visualstudio.com/docs/remote/wsl-tutorial
[remote-ssh]: https://code.visualstudio.com/docs/remote/ssh-tutorial
[rtd-git-guide]: ../git/index.md [rtd-git-guide]: ../git/index.md
[rtd-testing]: ../testing/testing.md [rtd-testing]: ../testing/testing.md
[rtd-using-dev-env]: using.md [rtd-using-dev-env]: using.md

2
docs/development/setup/vscode-vagrant.md
View File

@@ -8,7 +8,7 @@ $ code .
``` ```
to open VS Code connected to your Vagrant environment. See the to open VS Code connected to your Vagrant environment. See the
[Remote development over SSH][remote-ssh] tutorial for more information. [Remote development over SSH](https://code.visualstudio.com/docs/remote/ssh-tutorial) tutorial for more information.
When using this plugin with Vagrant, you will want to run the command When using this plugin with Vagrant, you will want to run the command
`vagrant ssh-config` from your `zulip` folder: `vagrant ssh-config` from your `zulip` folder:

4
docs/production/system-configuration.md
View File

@@ -97,6 +97,8 @@ If set to true, [configures Zulip to allow HTTP access][using-http];
use if Zulip is deployed behind a reverse proxy that is handling use if Zulip is deployed behind a reverse proxy that is handling
SSL/TLS termination. SSL/TLS termination.
[using-http]: reverse-proxies.md#configuring-zulip-to-allow-http
#### `nginx_listen_port` #### `nginx_listen_port`
Set to the port number if you [prefer to listen on a port other than Set to the port number if you [prefer to listen on a port other than
@@ -260,6 +262,8 @@ replicas](postgresql.md#postgresql-warm-standby). This is generally only set if
multiple warm standby replicas, in order to avoid taking multiple backups, one multiple warm standby replicas, in order to avoid taking multiple backups, one
per replica. per replica.
[wal-g]: export-and-import.md#database-only-backup-tools
#### `backups_disk_concurrency` #### `backups_disk_concurrency`
Number of concurrent disk reads to use when taking backups. Defaults to 1; you Number of concurrent disk reads to use when taking backups. Defaults to 1; you

2
docs/subsystems/logging.md
View File

@@ -35,6 +35,8 @@ Since 500 errors in any Zulip server are usually a problem the server
administrator should investigate and/or report upstream, we have this administrator should investigate and/or report upstream, we have this
email reporting system configured to report errors by default. email reporting system configured to report errors by default.
[django-errors]: https://docs.djangoproject.com/en/5.0/howto/error-reporting/
### Sentry error logging ### Sentry error logging
Zulip's optional backend [Sentry][sentry] integration will aggregate Zulip's optional backend [Sentry][sentry] integration will aggregate

2
docs/testing/continuous-integration.md
View File

@@ -82,6 +82,8 @@ the job. Once GitHub Actions fetches the image from Docker Hub, it will spin
up a docker container. See [images](#images) section to know more about up a docker container. See [images](#images) section to know more about
the images we use in GitHub Actions for testing. the images we use in GitHub Actions for testing.
[docker-hub]: https://hub.docker.com/r/zulip/ci
After booting the container from the configured image, GitHub Actions will After booting the container from the configured image, GitHub Actions will
create the directory mentioned in `working_directory` and all the create the directory mentioned in `working_directory` and all the
steps will be run from here. steps will be run from here.