summaryrefslogtreecommitdiff
path: root/doc/administration/invalidate_markdown_cache.md
diff options
context:
space:
mode:
authorJan Provaznik <jprovaznik@gitlab.com>2019-01-31 12:28:31 +0100
committerJan Provaznik <jprovaznik@gitlab.com>2019-02-06 19:46:59 +0100
commit433bcf9b0439771b1e2661a62fec115e44922232 (patch)
tree9587b4fb6cd4b87211b9f9a16d9e4c211a7d273f /doc/administration/invalidate_markdown_cache.md
parentd0187de202d94fa445a28c347b7a54dbf09a22a8 (diff)
downloadgitlab-ce-local-markdown-version.tar.gz
Add local markdown versionlocal-markdown-version
Cached markdown version is composed both from global and local markdown version. This allows admins to bump version locally when needed (e.g. when external URL is changed).
Diffstat (limited to 'doc/administration/invalidate_markdown_cache.md')
-rw-r--r--doc/administration/invalidate_markdown_cache.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/administration/invalidate_markdown_cache.md b/doc/administration/invalidate_markdown_cache.md
new file mode 100644
index 00000000000..ad64cb077c1
--- /dev/null
+++ b/doc/administration/invalidate_markdown_cache.md
@@ -0,0 +1,16 @@
+# Invalidate Markdown Cache
+
+For performance reasons, GitLab caches the HTML version of markdown text
+(e.g. issue and merge request descriptions, comments). It's possible
+that these cached versions become outdated, for example
+when the `external_url` configuration option is changed - causing links
+in the cached text to refer to the old URL.
+
+To avoid this problem, the administrator can invalidate the existing cache by
+increasing the `local_markdown_version` setting in application settings. This can
+be done by [changing the application settings through
+the API](../api/settings.md#change-application-settings):
+
+```bash
+curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?local_markdown_version=<increased_number>
+```