How to make extension login persistent across devices? about code-server HOT 6 OPEN

[...] the secret storage went browser-only [...]

– #6450

from code-server.

IMHO more extensions should allow reading their token from an environment variable.

from code-server.

Set token with environment variables

If you often delete your VS Code storage (such as in Gitpod containers) you can create environment variables before starting VS Code. If you set the token in an environment variable you don't have to set the personal access token every time you delete your VS Code storage.

• GITLAB_WORKFLOW_INSTANCE_URL: GitLab instance URL (e.g. https://gitlab.com).
• GITLAB_WORKFLOW_TOKEN: personal access token, which you created during setup.

The token configured in an environment variable is overridden if you configure a token for the same GitLab instance in the extension.

– GitLab Workflow

from code-server.

@code-asher @benz0li any thoughts on this?

from code-server.

We do patch user storage to go to disk instead of the browser so I think it would not be completely out of line to try moving secrets back to the disk as well, but I am not sure how easy it would be, and ideally we read both to prevent breaking existing secrets, or make it an option.

If it was made an option maybe we could even submit the idea upstream, surely Codespaces users might want to persist their credentials across multiple browsers/devices as well.

from code-server.

Although I guess upstream will probably just say to use settings sync, which is not an option for code-server from what I understand.

But does settings sync copy credentials as well? Not sure about that.

from code-server.