Persistent data stored in the wrong path #27

Closed
opened 2020-09-24 11:45:59 +00:00 by bclermont · 6 comments

/data is the volume mount path

but indexes and queues data are in /app/gitea/data, maybe the followings should be defaults in gitea.config in values.yaml ?

indexer:  ISSUE_INDEXER_PATH: /data/indexers/issues.bleve  ISSUE_INDEXER_QUEUE_DIR: /data/queues/issues.queue  REPO_INDEXER_PATH: /data/indexers/repos.bleve queue:  DATADIR: /data/queues/ repository:  ROOT: /data/repositories/ server:  LFS_CONTENT_PATH: /data/lfs  PROVIDER_CONFIG: /data/sessions picture:  AVATAR_UPLOAD_PATH: /data/avatars  REPOSITORY_AVATAR_UPLOAD_PATH: /data/avatars-repository attachment:  PATH: /data/attachments 
`/data` is the volume mount path but indexes and queues data are in `/app/gitea/data`, maybe the followings should be defaults in `gitea.config` in `values.yaml` ? ```yaml indexer: ISSUE_INDEXER_PATH: /data/indexers/issues.bleve ISSUE_INDEXER_QUEUE_DIR: /data/queues/issues.queue REPO_INDEXER_PATH: /data/indexers/repos.bleve queue: DATADIR: /data/queues/ repository: ROOT: /data/repositories/ server: LFS_CONTENT_PATH: /data/lfs PROVIDER_CONFIG: /data/sessions picture: AVATAR_UPLOAD_PATH: /data/avatars REPOSITORY_AVATAR_UPLOAD_PATH: /data/avatars-repository attachment: PATH: /data/attachments ```
Member

Hi, I will look into this next week, thanks for the suggestion !

Hi, I will look into this next week, thanks for the suggestion !
Member

we could use an optional second pvc here which will be mounted in app/gitea/data

I'm not sure if it is good to set default paths in the values, since i would like the default config == gitea default

we could use an optional second pvc here which will be mounted in app/gitea/data I'm not sure if it is good to set default paths in the values, since i would like the default config == gitea default
Author

we could use an optional second pvc here which will be mounted in app/gitea/data

that will be terrible, there is cost with extra PV in some cases

backup process become more complicated

I'm not sure if it is good to set default paths in the values, since i would like the default config == gitea default

you already changed gitea default by moving storage to /data

> we could use an optional second pvc here which will be mounted in app/gitea/data that will be terrible, there is cost with extra PV in some cases backup process become more complicated > I'm not sure if it is good to set default paths in the values, since i would like the default config == gitea default you already changed gitea default by moving storage to `/data`
Member

Could you not just set APP_DATA_PATH to /data?

Could you not just set APP_DATA_PATH to /data?
Member

Yeah, second PVC is a bad idea, you're right.

By changing the default I meant not having a bunch of predefined options in the values for the gitea config, sorry that was unclear.

Setting APP_DATA_PATH sounds like an easy and fast solution. Will give it a try tomorrow

Thanks

Yeah, second PVC is a bad idea, you're right. By changing the default I meant not having a bunch of predefined options in the values for the gitea config, sorry that was unclear. Setting APP_DATA_PATH sounds like an easy and fast solution. Will give it a try tomorrow Thanks
Member

Fixed with #37

Fixed with #37
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gitea/helm-gitea#27
No description provided.