feat: make VSCode user sign-in status persistent in container#3
Open
Senorsen wants to merge 1 commit intoaccetto:masterfrom
Open
feat: make VSCode user sign-in status persistent in container#3Senorsen wants to merge 1 commit intoaccetto:masterfrom
Senorsen wants to merge 1 commit intoaccetto:masterfrom
Conversation
…ume data Normally VSCode requires keyring softwares like gnome-keyring. We don't have this complex setup in our docker environment. This causes the user sign in data / status not persistent and when user opens a new VSCode instance / next time opens it, must need to sign in again. This change is fixing this issue by using the basic text encryption, although not recommend in normal desktop environments, but it suits the container environment very well. Also see: https://code.visualstudio.com/docs/configure/settings-sync#_other-linux-desktop-environments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Normally VSCode requires keyring softwares like gnome-keyring. We don't have this complex setup in our docker environment. This causes the user sign in data / status not persistent and when user opens a new VSCode instance / next time opens it, must need to sign in again.
This change is fixing this issue by using the basic text encryption, although not recommend in normal desktop environments, but it suits the container environment very well.
Also see: https://code.visualstudio.com/docs/configure/settings-sync#_other-linux-desktop-environments