Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GITBASE_READONLY env var #59

Merged
merged 1 commit into from
Jul 5, 2018
Merged

Conversation

carlosms
Copy link
Contributor

@carlosms carlosms commented Jul 3, 2018

Fix #58.

@@ -142,6 +142,8 @@ spec:
value: "{{ .Values.gitbaseServer.repositoriesDir }}"
- name: GITBASE_UNSTABLE_SQUASH_ENABLE
value: "{{ .Values.gitbaseServer.squashEnable }}"
- name: GITBASE_READONLY
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please enclose this in a conditional to avoid adding an empty env variable if gitbaseServer.readonly is empty

My bad for not having enforced this in your previous PR around GITBASE_UNSTABLE_SQUASH_ENABLE

@@ -77,6 +77,7 @@ gitbaseServer:
size: 10Gi
logLevel: debug
squashEnable: ""
readonly: ""
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment this out, just signaling it is a possibility to set it. It does not make sense to set env variables to empty values

Signed-off-by: Carlos Martín <carlos.martin.sanchez@gmail.com>
@carlosms
Copy link
Contributor Author

carlosms commented Jul 4, 2018

I've made the requested changes, rebasing to have 1 commit only.

@rporres
Copy link

rporres commented Jul 5, 2018

Thx for fixing the squash variable too 😍

@@ -140,8 +140,14 @@ spec:
value: "{{ .Values.gitbaseServer.logLevel }}"
- name: GITBASE_REPOS
value: "{{ .Values.gitbaseServer.repositoriesDir }}"
{{- if ..Values.gitbaseServer.squashEnable }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it work? Here is 2 dots...

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It shouldn't... Well spotted! 😅

@carlosms Can you please send a fix?

@smacker
Copy link
Contributor

smacker commented Jul 5, 2018

@rporres @carlosms could you please check squashing rule?

@rporres
Copy link

rporres commented Jul 5, 2018

@carlosms is on it

Thx, @smacker

@carlosms carlosms mentioned this pull request Jul 5, 2018
@carlosms
Copy link
Contributor Author

carlosms commented Jul 5, 2018

Good catch. Fix here: #61

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants