feat: Add option for a noindex meta tag on the HTML index page #1531

Open
s1lv3r wants to merge 3 commits from s1lv3r/continuwuity:1527-prevent-search-engine-indexing into ginger/password-reset
Contributor

Adds a new config option index_page_allow_indexing which defaults to false.

Fixes: !1527

News-fragment is TODO

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
Adds a new config option `index_page_allow_indexing` which defaults to false. Fixes: !1527 News-fragment is TODO <!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
feat: Add option for a noindex meta tag on the HTML index page
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m58s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
f15282569f
Adds a new config option `index_page_allow_indexing` which defaults to false.

Fixes: !1527
Jade approved these changes 2026-03-11 15:06:50 +00:00
Jade left a comment
Owner

Feel like this is going to have some conflicts with #1484 but otherwise looks good

Feel like this is going to have some conflicts with #1484 but otherwise looks good
chore: Add news fragment
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 16m28s
15a8cfe3d1
Author
Contributor

Hm yeah, you might be right.. Unsure what the best way to solve it is, possibly make this PR based on that one instead and wait for it to be merged first? Alternatively the changes are smallish, so wouldn't be too difficult to update that one if this gets merged first.

cc. @ginger, you might have feedback here?

Hm yeah, you might be right.. Unsure what the best way to solve it is, possibly make this PR based on that one instead and wait for it to be merged first? Alternatively the changes are smallish, so wouldn't be too difficult to update that one if this gets merged first. cc. @ginger, you might have feedback here?
Owner

You can probably make a pull request against ginger's branch so it gets merged in there. Not sure if you can edit this one though

You can probably make a pull request against ginger's branch so it gets merged in there. Not sure if you can edit this one though
Author
Contributor

I'm able to change the target of this one, gimme a sec + time to fix conflicts

I'm able to change the target of this one, gimme a sec + time to fix conflicts
s1lv3r changed target branch from main to ginger/password-reset 2026-03-11 15:14:26 +00:00
@ -111,4 +111,1 @@
"base_url": "https://matrix.example.com/"
},
"org.matrix.msc3575.proxy": {
"url": "https://matrix.example.com/"
Contributor

This doesn't seem related?

This doesn't seem related?
Author
Contributor

i believe its due to changing the target branch, this one is technically ahead of ginger/password-reset. I'm working on rebasing but its taking a sec, will likely be fixed when i push an updated branch

i believe its due to changing the target branch, this one is technically ahead of ginger/password-reset. I'm working on rebasing but its taking a sec, will likely be fixed when i push an updated branch
Owner

Yep. Three commits ahead

Yep. Three commits ahead
Jade marked this conversation as resolved
s1lv3r force-pushed 1527-prevent-search-engine-indexing from 15a8cfe3d1
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 16m28s
to 8575d8f3ff
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
2026-03-11 15:50:57 +00:00
Compare
s1lv3r force-pushed 1527-prevent-search-engine-indexing from 8575d8f3ff
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
to ded23b56ac
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
2026-03-11 15:52:29 +00:00
Compare
fix: Fix logic error
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m12s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 19m20s
86699add33
Author
Contributor

It doesn't error anymore, but I was unable to find a way to avoid specifying allow_indexing on every template. A solution like conduwuit_build_metadata::version_tag() won't work as these return static values from what i can see, and services.config.index_page_allow_indexing is dynamic.

It doesn't error anymore, but I was unable to find a way to avoid specifying `allow_indexing` on every template. A solution like `conduwuit_build_metadata::version_tag()` won't work as these return static values from what i can see, and `services.config.index_page_allow_indexing` is dynamic.
nex approved these changes 2026-03-13 12:04:44 +00:00
Owner

I need to take a look at this to see if there's a way to not pass allow_indexing to every template

I need to take a look at this to see if there's a way to not pass `allow_indexing` to every template
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m12s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 19m20s
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 1527-prevent-search-engine-indexing:s1lv3r-1527-prevent-search-engine-indexing
git switch s1lv3r-1527-prevent-search-engine-indexing

Merge

Merge the changes and update on Forgejo.
git switch ginger/password-reset
git merge --no-ff s1lv3r-1527-prevent-search-engine-indexing
git switch s1lv3r-1527-prevent-search-engine-indexing
git rebase ginger/password-reset
git switch ginger/password-reset
git merge --ff-only s1lv3r-1527-prevent-search-engine-indexing
git switch s1lv3r-1527-prevent-search-engine-indexing
git rebase ginger/password-reset
git switch ginger/password-reset
git merge --no-ff s1lv3r-1527-prevent-search-engine-indexing
git switch ginger/password-reset
git merge --squash s1lv3r-1527-prevent-search-engine-indexing
git switch ginger/password-reset
git merge --ff-only s1lv3r-1527-prevent-search-engine-indexing
git switch ginger/password-reset
git merge s1lv3r-1527-prevent-search-engine-indexing
git push origin ginger/password-reset
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1531
No description provided.