From d74e176cbee6fbe90b52dcd28074c4891b987093 Mon Sep 17 00:00:00 2001 From: Alex Vandiver Date: Tue, 21 Jan 2025 21:21:41 +0000 Subject: [PATCH] docs: Fix missing references. --- docs/development/setup-recommended.md | 1 - docs/development/setup/vscode-vagrant.md | 2 +- docs/production/system-configuration.md | 4 ++++ docs/subsystems/logging.md | 2 ++ docs/testing/continuous-integration.md | 2 ++ 5 files changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/development/setup-recommended.md b/docs/development/setup-recommended.md index 2d2a0fd44a..c2228e6bcf 100644 --- a/docs/development/setup-recommended.md +++ b/docs/development/setup-recommended.md @@ -1222,7 +1222,6 @@ remove the `GUEST_CPUS` and `GUEST_MEMORY_MB` lines from [vagrant-dl]: https://www.vagrantup.com/downloads.html [install-advanced]: setup-advanced.md [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-testing]: ../testing/testing.md [rtd-using-dev-env]: using.md diff --git a/docs/development/setup/vscode-vagrant.md b/docs/development/setup/vscode-vagrant.md index a83e549f70..a9634f021e 100644 --- a/docs/development/setup/vscode-vagrant.md +++ b/docs/development/setup/vscode-vagrant.md @@ -8,7 +8,7 @@ $ code . ``` 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 `vagrant ssh-config` from your `zulip` folder: diff --git a/docs/production/system-configuration.md b/docs/production/system-configuration.md index 22e1c93339..95c13f52c6 100644 --- a/docs/production/system-configuration.md +++ b/docs/production/system-configuration.md @@ -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 SSL/TLS termination. +[using-http]: reverse-proxies.md#configuring-zulip-to-allow-http + #### `nginx_listen_port` 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 per replica. +[wal-g]: export-and-import.md#database-only-backup-tools + #### `backups_disk_concurrency` Number of concurrent disk reads to use when taking backups. Defaults to 1; you diff --git a/docs/subsystems/logging.md b/docs/subsystems/logging.md index 5404263738..edfa4e94de 100644 --- a/docs/subsystems/logging.md +++ b/docs/subsystems/logging.md @@ -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 email reporting system configured to report errors by default. +[django-errors]: https://docs.djangoproject.com/en/5.0/howto/error-reporting/ + ### Sentry error logging Zulip's optional backend [Sentry][sentry] integration will aggregate diff --git a/docs/testing/continuous-integration.md b/docs/testing/continuous-integration.md index 043cb8cd0d..077819964c 100644 --- a/docs/testing/continuous-integration.md +++ b/docs/testing/continuous-integration.md @@ -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 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 create the directory mentioned in `working_directory` and all the steps will be run from here.