Replies: 2 comments · 4 replies
|
I believe git will take the |
|
It is, but unfortunately adding those to my manifest didn't work. The env vars are available within the container ( |
|
Oh hmm. When you run I am not sure how to test Kubernetes but I tried running code-server on its own like this: And it seems to work in code-server's integrated terminal: I also tried from the git side panel in the UI and that also worked with the right username. So maybe there is something wrong with how |
|
So although I'm running it in kubernetes, I haven't used the Helm chart - I built a manifest based on the docker compose settings. My manifest is below: # =========================
# CODE-SERVER
# =========================
apiVersion: apps/v1
kind: Deployment
metadata:
name: code-server
namespace: code-server
spec:
replicas: 1
selector:
matchLabels:
app: code-server
template:
metadata:
labels:
app: code-server
spec:
containers:
- name: code-server
image: codercom/code-server:4.115.0-39
ports:
- containerPort: 8080
name: http
env:
- name: GIT_AUTHOR_NAME
value: "[name]"
- name: GIT_AUTHOR_EMAIL
value: "[email]"
volumeMounts:
- name: config
mountPath: /home/coder/.config
- name: local
mountPath: /home/coder/.local
- name: project
mountPath: /home/coder/project
volumes:
- name: config
hostPath:
path: /mnt/k3s/config/code-server
type: DirectoryOrCreate
- name: local
hostPath:
path: /mnt/k3s/code-server/local
type: DirectoryOrCreate
- name: project
hostPath:
path: /mnt/scripts
type: DirectoryOrCreate
---
|
|
Ahh gotcha. Hmm from what little I know that does look correct... |
|
I ran into this same thing last year with code-server in Kubernetes. The key insight is that git will respect GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL environment variables when set. You can set these via code-server's extraVars configuration in your Kubernetes deployment. Here's how:
extraEnv:
- name: GIT_AUTHOR_NAME
value: "Your Name"
- name: GIT_AUTHOR_EMAIL
value: "your.email@example.com"
helm install code-server coder/code-server \
--set extraEnv[0].name=GIT_AUTHOR_NAME \
--set extraEnv[0].value="Your Name" \
--set extraEnv[1].name=GIT_AUTHOR_EMAIL \
--set extraEnv[1].value="your.email@example.com"This approach works because:
|
Uh oh!
There was an error while loading. Please reload this page.
I am running code-server in a Kubernetes cluster, and so its entirely possible that the pods hosting it might be recreated at any point. The git config is local and, to the best of my knowledge, not stored in the code-server config. Therefore, if the pod is recreated the git config will be destroyed and I'd have to re-enter it.
Am I missing something? I couldn't find anything in the docs about how to set the Env variables to recreate these configuration items on a rebuild.
All reactions