lunny/helm-chart
1
0
Fork 1
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

Enable git uploadpack filter #254

New Issue
Closed
opened 2021-11-23 13:36:04 +00:00 by viceice · 4 comments
viceice commented 2021-11-23 13:36:04 +00:00 (Migrated from gitea.com)
Copy Link

https://git-scm.com/docs/git-config#Documentation/git-config.txt-GITCONFIGCOUNT
https://docs.gitea.io/en-us/clone-filters/

This is my workaround ?

statefulset:
  env:
    - name: GIT_CONFIG_COUNT
      value: '1'
    - name: GIT_CONFIG_KEY_0
      value: uploadpack.allowfilter
    - name: GIT_CONFIG_VALUE_0
      value: 'true'
https://git-scm.com/docs/git-config#Documentation/git-config.txt-GITCONFIGCOUNT https://docs.gitea.io/en-us/clone-filters/ This is my workaround ? ```yaml statefulset: env: - name: GIT_CONFIG_COUNT value: '1' - name: GIT_CONFIG_KEY_0 value: uploadpack.allowfilter - name: GIT_CONFIG_VALUE_0 value: 'true' ```
viceice commented 2021-11-23 13:45:59 +00:00 (Migrated from gitea.com)
Copy Link

The workaround doesn't seem to work, looks like gitea isn't passing that to git exec.

The workaround doesn't seem to work, looks like gitea isn't passing that to git exec.
viceice commented 2021-11-23 14:21:15 +00:00 (Migrated from gitea.com)
Copy Link

OK, It's caused by a to old git v2.30.2 on gitea docker image.

So setting GIT_CONFIG_GLOBAL didn't work either.

So my now working stuff is mounting HOME to data

extraVolumeMounts:
  # override home to allow configure static git config
  - name: data
    subPath: git
    mountPath: /var/lib/gitea/git

So i have a persistent git config.

OK, It's caused by a to old git v2.30.2 on gitea docker image. So setting `GIT_CONFIG_GLOBAL` didn't work either. So my now working stuff is mounting HOME to data ```yaml extraVolumeMounts: # override home to allow configure static git config - name: data subPath: git mountPath: /var/lib/gitea/git ``` So i have a persistent git config.
justusbunsi commented 2021-11-23 15:57:17 +00:00 (Migrated from gitea.com)
Copy Link

If you like, you could open another issue for configuring the whole .gitconfig for Gitea or adjust this one. There are some good reasons (yours included) to support that in the Chart.
That way it would not be specific for one git configuration.

If you like, you could open another issue for configuring the whole `.gitconfig` for Gitea or adjust this one. There are some good reasons (yours included) to support that in the Chart. That way it would not be specific for one git configuration.
viceice commented 2021-11-23 17:37:29 +00:00 (Migrated from gitea.com)
Copy Link

OK, closing in favor of #255

OK, closing in favor of #255
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
has/backport
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/other
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lunny
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#254
No description provided.
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?