The effort you are putting to create samples and guides, may be worth putting to maintain a non-HA version. It reduces error and easier to troubleshoot.
I've been using this helm chart for…
If you are getting Failed to create queue "notification-service": invalid leveldb connection string try this in values.yaml
gitea:
config:
queue:
TYPE: channel
…UPDATE: Just tried to upgrade to v9 and failed because it went over the volume that can be attached to a node. Redis cluster is set to have 6 pods, each require a PV that uses the majority volume…
Thanks @justusbunsi Yeah I understand, it may double up your work.
One of my main decision factor to migrate to gitea was the light-weight nature and simplicity. It was a definite win over…
@justusbunsi I can confirm by setting SSH log level (https://gitea.com/pi3ch/helm-chart/src/branch/main/values.yaml#L352) to FATAL the logs are not shown but I don't think this has addressed the…
OK, I managed to get things working with PG 15 (it was also okay to continue using PG 11 but helm upgrade fail).
It was not a straight forward upgrade due to some issue which I explain…
OK. so I endded up in a bit of drama. Gitea was upgraded to 1.19 and hence db tables has been upgraded on PG 11.
Uninstalled and reinstalled helm chart.
PG 15 could load due to change with…
9d5cf4c5b2
Merge pull request 'Move SSH_LOG_LEVEL to ssh related object' (#1) from justusbunsi/helm-chart:ssh-env into main
@justusbunsi Gitea UI is all new to me. where can I find exclusive write PR? I've just pressed "Update by merge", unsure that added your changes.
I didn't setup any branch protection, was just…
@pi3ch With regards to Chart maintainability I would like to prevent a quick fix resulting in a breaking change or at least inconsistency when adding related features such as #321.
Do you…
I personally don't mind and either option is fine with me. Perhaps it is better we cast vote and decide on this so this MR can get in soon.
I found all SSH related settings under Server section of the cheatsheet (https://docs.gitea.io/en-us/config-cheat-sheet/#server-server) so it made sense to keep the SSH settings all in once…