8fb477a6e7
up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information (cherry picked from commit 2b7016cc56d12e67de9f1f25b18311866a26a5fe)
31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
# redirect rules for paths (server-side) to prevent link rot.
|
|
# see ./redirects.js for redirects based on URL fragments (client-side)
|
|
#
|
|
# concrete user story this supports:
|
|
# - user finds URL to the manual for Nix x.y
|
|
# - Nix x.z (z > y) is the most recent release
|
|
# - updating the version in the URL will show the right thing
|
|
#
|
|
# format documentation:
|
|
# - https://docs.netlify.com/routing/redirects/#syntax-for-the-redirects-file
|
|
# - https://docs.netlify.com/routing/redirects/redirect-options/
|
|
#
|
|
# conventions:
|
|
# - always force (<CODE>!) since this allows re-using file names
|
|
# - group related paths to ease readability
|
|
# - always append new redirects to the end of the file
|
|
# - redirects that should have been there but are missing can be inserted where they belong
|
|
|
|
/expressions/expression-language /language/ 301!
|
|
/expressions/language-values /language/values 301!
|
|
/expressions/language-constructs /language/constructs 301!
|
|
/expressions/language-operators /language/operators 301!
|
|
/expressions/* /language/:splat 301!
|
|
|
|
/package-management/basic-package-mgmt /command-ref/nix-env 301!
|
|
|
|
/package-management/channels* /command-ref/nix-channel 301!
|
|
|
|
/package-management/s3-substituter* /command-ref/new-cli/nix3-help-stores#s3-binary-cache-store 301!
|
|
|