github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-18 22:22:24 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Requesting search of wiki repos #1624

New Issue
Open
opened 2025-11-02 04:07:12 -06:00 by GiteaMirror · 22 comments
GiteaMirror commented 2025-11-02 04:07:12 -06:00
Owner
Copy Link

Originally created by @nathan-sain on GitHub (Mar 14, 2018).

Originally assigned to: @6543 on GitHub.

  • Gitea version (or commit ref):9a5e628 (Gitea Docker container)
  • Git version: 2.15.0
  • Operating system:Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant (Unable to connect)
  • Log gist:

Description

I have enabled indexing of my repos with
REPO_INDEXER_ENABLED = true
in my app.ini
I would like to search my wiki repos like I do my code repos

Originally created by @nathan-sain on GitHub (Mar 14, 2018). Originally assigned to: @6543 on GitHub. <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref):9a5e628 (Gitea Docker container) - Git version: 2.15.0 - Operating system:Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant (Unable to connect) - Log gist: ## Description I have enabled indexing of my repos with REPO_INDEXER_ENABLED = true in my app.ini I would like to search my wiki repos like I do my code repos
GiteaMirror added the type/featureissue/confirmed labels 2025-11-02 04:07:12 -06:00
GiteaMirror commented 2025-11-02 04:07:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 14, 2018):

Currently it will only index code but not related wiki repo.

@lunny commented on GitHub (Mar 14, 2018): Currently it will only index code but not related wiki repo.
GiteaMirror commented 2025-11-02 04:07:13 -06:00
Author
Owner
Copy Link

@igsol commented on GitHub (Nov 6, 2018):

@lunny

not related wiki repo.

Ah, how it's pity 😢

@igsol commented on GitHub (Nov 6, 2018): @lunny > not related wiki repo. Ah, how it's pity :cry:
GiteaMirror commented 2025-11-02 04:07:13 -06:00
Author
Owner
Copy Link

@zettar commented on GitHub (Nov 6, 2018):

not related wiki repo.

Ah, how it's pity 😢

Second the above.

@zettar commented on GitHub (Nov 6, 2018): > not related wiki repo. >> Ah, how it's pity :cry: Second the above.
GiteaMirror commented 2025-11-02 04:07:14 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 5, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 5, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:07:14 -06:00
Author
Owner
Copy Link

@fangchin commented on GitHub (Jan 5, 2019):

Indexing wiki and having an effective search function definitely helps with the use of a software, especially something as promising as gitea. Please give this ticket more consideration that it deserves.

@fangchin commented on GitHub (Jan 5, 2019): Indexing wiki and having an effective search function definitely helps with the use of a software, especially something as promising as gitea. Please give this ticket more consideration that it deserves.
GiteaMirror commented 2025-11-02 04:07:14 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:07:15 -06:00
Author
Owner
Copy Link

@mrsdizzie commented on GitHub (Mar 6, 2019):

Agree this feature is sorely missing and makes the wiki not very useable in lots of real world situations (lots of documentation/text isn't practical without search). It is almost more usable to use the regular code view to store the wiki/md files where you get access to search but loose the few wiki features like page dropdown and _sidebar/_footer

Having a search here would make the wiki feature exponentially more useful :)

@mrsdizzie commented on GitHub (Mar 6, 2019): Agree this feature is sorely missing and makes the wiki not very useable in lots of real world situations (lots of documentation/text isn't practical without search). It is almost more usable to use the regular code view to store the wiki/md files where you get access to search but loose the few wiki features like page dropdown and _sidebar/_footer Having a search here would make the wiki feature exponentially more useful :)
GiteaMirror commented 2025-11-02 04:07:15 -06:00
Author
Owner
Copy Link

@oscarlofwenhamn commented on GitHub (Mar 28, 2019):

This would be a very useful feature indeed!

@oscarlofwenhamn commented on GitHub (Mar 28, 2019): This would be a very useful feature indeed!
GiteaMirror commented 2025-11-02 04:07:16 -06:00
Author
Owner
Copy Link

@paolo-rendano commented on GitHub (Aug 28, 2019):

Any progress on this? Search on wiki is a must for this kind of tool.

Thanks
Paolo

@paolo-rendano commented on GitHub (Aug 28, 2019): Any progress on this? Search on wiki is a must for this kind of tool. Thanks Paolo
GiteaMirror commented 2025-11-02 04:07:16 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Aug 28, 2019):

Could it be implemented with bleve, like the other searches? Any objections with an implementation like that? I guess the Wiki is just markdown code, so I think it shouldn't be too difficult to implement.

@guillep2k commented on GitHub (Aug 28, 2019): Could it be implemented with bleve, like the other searches? Any objections with an implementation like that? I guess the Wiki is just markdown code, so I think it shouldn't be too difficult to implement.
GiteaMirror commented 2025-11-02 04:07:16 -06:00
Author
Owner
Copy Link

@oscarlofwenhamn commented on GitHub (Aug 28, 2019):

The wikis being just (afaik) rendered code, it definitely feels like it should be able to be done in a similar fashion.

@oscarlofwenhamn commented on GitHub (Aug 28, 2019): The wikis being just (afaik) rendered code, it definitely feels like it should be able to be done in a similar fashion.
GiteaMirror commented 2025-11-02 04:07:17 -06:00
Author
Owner
Copy Link

@MasterDimmy commented on GitHub (Dec 22, 2020):

requesting for this

@MasterDimmy commented on GitHub (Dec 22, 2020): requesting for this
GiteaMirror commented 2025-11-02 04:07:17 -06:00
Author
Owner
Copy Link

@nauevg commented on GitHub (Jun 23, 2021):

Any updates on this?

@nauevg commented on GitHub (Jun 23, 2021): Any updates on this?
GiteaMirror commented 2025-11-02 04:07:18 -06:00
Author
Owner
Copy Link

@Abyss777 commented on GitHub (May 26, 2022):

Very useful feature. Any plans to implement this?

@Abyss777 commented on GitHub (May 26, 2022): Very useful feature. Any plans to implement this?
GiteaMirror commented 2025-11-02 04:07:18 -06:00
Author
Owner
Copy Link

@johand77 commented on GitHub (Aug 22, 2022):

Would definitely love this feature. That makes the wiki a much more powerfull tool for documentation.

@johand77 commented on GitHub (Aug 22, 2022): Would definitely love this feature. That makes the wiki a much more powerfull tool for documentation.
GiteaMirror commented 2025-11-02 04:07:19 -06:00
Author
Owner
Copy Link

@theobjectivedad commented on GitHub (Sep 7, 2022):

I'd love to see this on the roadmap!

@theobjectivedad commented on GitHub (Sep 7, 2022): I'd love to see this on the roadmap!
GiteaMirror commented 2025-11-02 04:07:19 -06:00
Author
Owner
Copy Link

@ivptr commented on GitHub (Feb 18, 2023):

Any update on this?

@ivptr commented on GitHub (Feb 18, 2023): Any update on this?
GiteaMirror commented 2025-11-02 04:07:19 -06:00
Author
Owner
Copy Link

@Darthagnon commented on GitHub (Sep 9, 2023):

I, too, would love to see this on the roadmap - I currently maintain a company wiki within Gitea, but the lack of search is sorely missing.

@Darthagnon commented on GitHub (Sep 9, 2023): I, too, would love to see this on the roadmap - I currently maintain a company wiki within Gitea, but the lack of search is sorely missing.
GiteaMirror commented 2025-11-02 04:07:20 -06:00
Author
Owner
Copy Link

@RyanGreenup commented on GitHub (Oct 13, 2023):

Like a few others have mentioned, I too create a separate code repository and use it as a wiki. However, the analyzer uses keyword rather than standard 1 making the search less ideal (e.g. python returns results but the query python list does not, see generally 2 ).

Long-term there needs to be a separate indexer for the wiki but for an easy workaround one can change the analyzer used in the source:

sed -i  's!analyzer/keyword!analyzer/standard!'  modules/indexer/code/bleve/bleve.go

I put together this Dockerfile if anybody wants to use it:

FROM codeberg.org/forgejo/forgejo:1.20


# Install Go (needed because alpine currently has 1.20)
RUN wget 'https://go.dev/dl/go1.21.3.linux-amd64.tar.gz'
RUN tar -C /usr/local -xzf go1.21.3.linux-amd64.tar.gz
ENV PATH="/usr/local/go/bin/:$PATH"
ENV CGO_ENABLED=1

# Install dependencies
RUN apk update; apk add make nodejs npm gcc musl-dev

# Get the source and patch it
RUN git clone https://codeberg.org/forgejo/forgejo --depth=1
RUN sed -i  's!analyzer/keyword!analyzer/standard!'  forgejo/modules/indexer/code/bleve/bleve.go

# Build it
RUN cd forgejo; make clean-all
RUN cd forgejo; make frontend
RUN cd forgejo; go build contrib/environment-to-ini/environment-to-ini.go
RUN cd forgejo; TAGS="bindata sqlite sqlite_unlock_notify" make -j1

# Install it
RUN install -Dm755 forgejo/gitea -t /usr/local/bin/
@RyanGreenup commented on GitHub (Oct 13, 2023): Like a few others have mentioned, I too create a separate code repository and use it as a wiki. However, the analyzer uses [`keyword`](https://github.com/blevesearch/bleve/blob/master/analysis/analyzer/keyword/keyword.go) rather than [`standard`](https://github.com/blevesearch/bleve/blob/master/analysis/analyzer/standard/standard.go) [^1] making the search less ideal (e.g. `python` returns results but the query `python list` does not, see generally [^3]). Long-term there needs to be a separate indexer for the wiki but for an easy workaround one can change the analyzer used in the source: ```sh sed -i 's!analyzer/keyword!analyzer/standard!' modules/indexer/code/bleve/bleve.go ``` I put together this `Dockerfile` if anybody wants to use it: <details> ```dockerfile FROM codeberg.org/forgejo/forgejo:1.20 # Install Go (needed because alpine currently has 1.20) RUN wget 'https://go.dev/dl/go1.21.3.linux-amd64.tar.gz' RUN tar -C /usr/local -xzf go1.21.3.linux-amd64.tar.gz ENV PATH="/usr/local/go/bin/:$PATH" ENV CGO_ENABLED=1 # Install dependencies RUN apk update; apk add make nodejs npm gcc musl-dev # Get the source and patch it RUN git clone https://codeberg.org/forgejo/forgejo --depth=1 RUN sed -i 's!analyzer/keyword!analyzer/standard!' forgejo/modules/indexer/code/bleve/bleve.go # Build it RUN cd forgejo; make clean-all RUN cd forgejo; make frontend RUN cd forgejo; go build contrib/environment-to-ini/environment-to-ini.go RUN cd forgejo; TAGS="bindata sqlite sqlite_unlock_notify" make -j1 # Install it RUN install -Dm755 forgejo/gitea -t /usr/local/bin/ ``` </details> [^1]: https://codeberg.org/forgejo/forgejo/src/branch/v1.21/forgejo/modules/indexer/code/bleve/bleve.go#L29 [^3]: https://bleveanalysis.couchbase.com/static/
GiteaMirror commented 2025-11-02 04:07:20 -06:00
Author
Owner
Copy Link

@0e39bf7b commented on GitHub (Nov 19, 2023):

Hello! Are there any plans on this feature?

@0e39bf7b commented on GitHub (Nov 19, 2023): Hello! Are there any plans on this feature?
GiteaMirror commented 2025-11-02 04:07:20 -06:00
Author
Owner
Copy Link

@RyanGreenup commented on GitHub (Feb 10, 2024):

In hindsight I'm not sure if my last workaround worked very well, I'd need to review it.

What needs to be done to implement this? If someone with more experience in this codebase can list some achievable steps, I'm happy to help out in any way I can.

As it stands I'm using a separate Meilisearch Bar and fzf + bleve, I'd rather just use the integrated bleve.

@RyanGreenup commented on GitHub (Feb 10, 2024): In hindsight I'm not sure if my [last workaround](https://github.com/go-gitea/gitea/issues/3670#issuecomment-1760782455) worked very well, I'd need to review it. What needs to be done to implement this? If someone with more experience in this codebase can list some achievable steps, I'm happy to help out in any way I can. As it stands I'm using a separate Meilisearch Bar and [fzf + bleve](https://gitlab.com/RyanGreenup/note_taking), I'd rather just use the integrated bleve.
GiteaMirror commented 2025-11-02 04:07:21 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Mar 12, 2024):

suggestions how to expose it to the ui are welcome to #29726 ;)

@6543 commented on GitHub (Mar 12, 2024): suggestions how to expose it to the ui are welcome to #29726 ;)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1624
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?