Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Gitea
  3. Enabling Gitea Indexer fails due to read-only file system

Enabling Gitea Indexer fails due to read-only file system

Scheduled Pinned Locked Moved Gitea
3 Posts 2 Posters 8.8k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ChristopherMagC Offline
      ChristopherMagC Offline
      ChristopherMag
      wrote on last edited by ChristopherMag
      #1

      Gitea supports indexer's so that you can search across the content of the code stored in Gitea.

      The default configuration in the docs is to add the following to the app.ini file:

      [indexer]
      ; ...
      REPO_INDEXER_ENABLED = true
      REPO_INDEXER_PATH = indexers/repos.bleve
      UPDATE_BUFFER_LEN = 20
      MAX_FILE_SIZE = 1048576
      REPO_INDEXER_INCLUDE =
      REPO_INDEXER_EXCLUDE = resources/bin/**
      

      After adding this to and restarting the app I get the following errors in the logs:

      ...er/issues/indexer.go:173:func2() [I] [644ad75f-12] PID 167: Initializing Issue Indexer: bleve
      ...exer/code/indexer.go:186:func3() [I] [644ad75f-14] PID: 167 Initializing Repository Indexer at: /home/git/gitea/indexers/repos.bleve
      ...xer/stats/indexer.go:38:populateRepoIndexer() [I] Populating the repo stats indexer with existing repositories
      ...ndexer/code/bleve.go:273:Close() [I] [644ad75f-14] PID: 167 Repository Indexer closed
      ...exer/code/indexer.go:200:func3() [F] [644ad75f-14] PID: 167 Unable to initialize the bleve Repository Indexer at path: /home/git/gitea/indexers/repos.bleve Error: mkdir /home/git/gitea/indexers: read-only file system
      ...exer/code/indexer.go:265:func4() [W] [644ad75f-14] Repository Indexer Initialization failed
      341 INFO exited: gitea (exit status 1; not expected)
      

      The main heart of the problem I believe is Unable to initialize the bleve Repository Indexer at path: /home/git/gitea/indexers/repos.bleve Error: mkdir /home/git/gitea/indexers: read-only file system.

      In the start.sh file it has crudini --set "/run/gitea/app.ini" indexer ISSUE_INDEXER_PATH "/app/data/appdata/indexers/issues.bleve" which appears to configure the path for the indexer that indexs issues but maybe there is another setting that needs to be set correctly.

      ChristopherMagC 1 Reply Last reply
      1
      • ChristopherMagC ChristopherMag

        Gitea supports indexer's so that you can search across the content of the code stored in Gitea.

        The default configuration in the docs is to add the following to the app.ini file:

        [indexer]
        ; ...
        REPO_INDEXER_ENABLED = true
        REPO_INDEXER_PATH = indexers/repos.bleve
        UPDATE_BUFFER_LEN = 20
        MAX_FILE_SIZE = 1048576
        REPO_INDEXER_INCLUDE =
        REPO_INDEXER_EXCLUDE = resources/bin/**
        

        After adding this to and restarting the app I get the following errors in the logs:

        ...er/issues/indexer.go:173:func2() [I] [644ad75f-12] PID 167: Initializing Issue Indexer: bleve
        ...exer/code/indexer.go:186:func3() [I] [644ad75f-14] PID: 167 Initializing Repository Indexer at: /home/git/gitea/indexers/repos.bleve
        ...xer/stats/indexer.go:38:populateRepoIndexer() [I] Populating the repo stats indexer with existing repositories
        ...ndexer/code/bleve.go:273:Close() [I] [644ad75f-14] PID: 167 Repository Indexer closed
        ...exer/code/indexer.go:200:func3() [F] [644ad75f-14] PID: 167 Unable to initialize the bleve Repository Indexer at path: /home/git/gitea/indexers/repos.bleve Error: mkdir /home/git/gitea/indexers: read-only file system
        ...exer/code/indexer.go:265:func4() [W] [644ad75f-14] Repository Indexer Initialization failed
        341 INFO exited: gitea (exit status 1; not expected)
        

        The main heart of the problem I believe is Unable to initialize the bleve Repository Indexer at path: /home/git/gitea/indexers/repos.bleve Error: mkdir /home/git/gitea/indexers: read-only file system.

        In the start.sh file it has crudini --set "/run/gitea/app.ini" indexer ISSUE_INDEXER_PATH "/app/data/appdata/indexers/issues.bleve" which appears to configure the path for the indexer that indexs issues but maybe there is another setting that needs to be set correctly.

        ChristopherMagC Offline
        ChristopherMagC Offline
        ChristopherMag
        wrote on last edited by
        #2

        @ChristopherMag

        The fix is to change REPO_INDEXER_PATH = indexers/repos.bleve to REPO_INDEXER_PATH = /app/data/appdata/indexers/repos.bleve.

        Please go ahead and mark this as solved but I wanted to still post it in case it is useful for someone else.

        Describing the problem led to the obvious solution :-).

        girishG 1 Reply Last reply
        3
        • ChristopherMagC ChristopherMag

          @ChristopherMag

          The fix is to change REPO_INDEXER_PATH = indexers/repos.bleve to REPO_INDEXER_PATH = /app/data/appdata/indexers/repos.bleve.

          Please go ahead and mark this as solved but I wanted to still post it in case it is useful for someone else.

          Describing the problem led to the obvious solution :-).

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          @ChristopherMag thanks!

          1 Reply Last reply
          0
          • girishG girish moved this topic from Support on
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search