From ac2c4a4871e90ddfb180f23704ce7ec9023529ca Mon Sep 17 00:00:00 2001 From: Maurice <14877287+MauriceBrg@users.noreply.github.com> Date: Sun, 14 Jun 2020 15:51:19 +0200 Subject: [PATCH] Update documentation for Ugly URLs (#1082) * Update urls.md Update documentation to reflect status of this issue - (the --uglyurls CLI parameter no longer exists) https://github.com/gohugoio/hugo/issues/4428 See also: https://gohugo.io/getting-started/configuration/#configure-with-environment-variables * Update urls.md Remove a "use" that was not necessary. --- content/en/content-management/urls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/content-management/urls.md b/content/en/content-management/urls.md index c4afbe0b7..4389b1dca 100644 --- a/content/en/content-management/urls.md +++ b/content/en/content-management/urls.md @@ -209,7 +209,7 @@ content/posts/post-1.md ## Ugly URLs -If you would like to have what are often referred to as "ugly URLs" (e.g., example.com/urls.html), set `uglyurls = true` or `uglyurls: true` in your site's `config.toml` or `config.yaml`, respectively. You can also use the `--uglyURLs=true` [flag from the command line][usage] with `hugo` or `hugo server`. +If you would like to have what are often referred to as "ugly URLs" (e.g., example.com/urls.html), set `uglyurls = true` or `uglyurls: true` in your site's `config.toml` or `config.yaml`, respectively. You can also set the `HUGO_UGLYURLS` environment variable to `true` when running `hugo` or `hugo server`. If you want a specific piece of content to have an exact URL, you can specify this in the [front matter][] under the `url` key. The following are examples of the same content directory and what the eventual URL structure will be when Hugo runs with its default behavior.