We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
code-server --version
Do not delete profile data on the remote and sync/init from it when visited from another browser.
Profiles are getting deleted on each different browser.
No response
I did not test native VS Code
I did not test GitHub Codespaces
code-server is running in a container with unix socket configuration and accessed over nginx that runs on another container.
The text was updated successfully, but these errors were encountered:
Is the profile stored on the remote server or in the browser's local storage?
Sorry, something went wrong.
Cross reference:
Profile's configuration files (settings.json, extensions.js ...) is on the remote, '~/.local/share/code-server/User/profiles/profileid/'.
Profiles are stored in the browser's local storage. Cross reference:
It's acceptable to set same configuration on each browser if it would be possible to make them don't overwrite other's configurations.
I am experiencing this issue as well. Can’t use profiles with multiple browsers at the moment.
No branches or pull requests
Is there an existing issue for this?
OS/Web Information
code-server --version
: 4.96.2Steps to Reproduce
Expected
Do not delete profile data on the remote and sync/init from it when visited from another browser.
Actual
Profiles are getting deleted on each different browser.
Logs
Screenshot/Video
No response
Does this bug reproduce in native VS Code?
I did not test native VS Code
Does this bug reproduce in GitHub Codespaces?
I did not test GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
code-server is running in a container with unix socket configuration and accessed over nginx that runs on another container.
The text was updated successfully, but these errors were encountered: