gitea-1.14.x-updates #148

Merged
luhahn merged 10 commits from gitea-1.14.x-updates into master 2021-04-29 09:12:48 +00:00
Member

This PR includes the changes from:

In addition it adds the possibility to include secrets via environment variables as mentioned in #60

This PR includes the changes from: - https://gitea.com/gitea/helm-chart/pulls/129 - https://gitea.com/gitea/helm-chart/pulls/140 In addition it adds the possibility to include secrets via environment variables as mentioned in #60
luhahn added 7 commits 2021-04-23 13:07:09 +00:00
luhahn added 1 commit 2021-04-23 13:38:28 +00:00
Update Readme
All checks were successful
continuous-integration/drone/pr Build is passing
0cdb33540d
techknowlogick approved these changes 2021-04-23 15:10:00 +00:00
luhahn added 1 commit 2021-04-26 08:01:03 +00:00
Fix import secrets as environment variables in main container
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone/pr Build is passing
0b73a99260
Author
Member

Now completly testet on multiple clusters including automigration and environment variable secret import

Now completly testet on multiple clusters including automigration and environment variable secret import
zeripath reviewed 2021-04-28 08:20:20 +00:00
README.md Outdated
@@ -35,0 +41,4 @@
However, this will not happen, if:
- You've got gitea.config.repository.ROOT defined
Member

If this value is set then they are not affected by the change in default value behaviour as they are already overriding the default.

If this value is set then they are not affected by the change in default value behaviour as they are already overriding the default.
luhahn marked this conversation as resolved
zeripath reviewed 2021-04-28 08:21:33 +00:00
README.md Outdated
@@ -35,0 +42,4 @@
However, this will not happen, if:
- You've got gitea.config.repository.ROOT defined
- You've set gitea.automigration: false
Member

I'm not certain this is necessary. Can't they just set gitea.config.repository.ROOT to where they want it?

I'm not certain this is necessary. Can't they just set gitea.config.repository.ROOT to where they want it?
Author
Member

True, since this is a one time action we should not automate it.
I was overthinking this :D

True, since this is a one time action we should not automate it. I was overthinking this :D
luhahn marked this conversation as resolved
luhahn force-pushed gitea-1.14.x-updates from 0b73a99260 to 655b9ff7fc 2021-04-29 07:59:44 +00:00 Compare
luhahn force-pushed gitea-1.14.x-updates from 655b9ff7fc to 5379c93e5b 2021-04-29 08:01:28 +00:00 Compare
zeripath reviewed 2021-04-29 08:15:18 +00:00
README.md Outdated
@@ -415,6 +438,7 @@ Annotations can be added to the Gitea pod.
| Parameter | Description | Default |
|---------------------|-----------------------------------|------------------------------|
|gitea.automigrate | Automatically migrate from pre 1.14 to 1.14.x | true |
Member

Is this now out-of-date?

Is this now out-of-date?
luhahn marked this conversation as resolved
luhahn force-pushed gitea-1.14.x-updates from 6337ee37c8 to 09a1baec13 2021-04-29 09:01:32 +00:00 Compare
zeripath approved these changes 2021-04-29 09:06:29 +00:00
luhahn merged commit b88bbd6d4d into master 2021-04-29 09:12:48 +00:00
luhahn referenced this issue from a commit 2021-04-29 09:12:49 +00:00
Sign in to join this conversation.
No description provided.