code-server: settings.json in code server v3.6.2 and v3.6.1 is no longer populated.
- Web Browser: Chrome latest
- Local OS: Mac latest
- Remote OS: Linux
- Remote Architecture: google cloud vm
code-server --version: 3.6.2 and 3.6.1
Recently upgraded to v3.6.2.
one thing seems a bit odd is that the settings.json was supposed to be populated under this directory: ~/.local/share/code-server/User if user has any vscode related settings change like a color theme.
the settings.json file was there in~/.local/share/code-server/User under v3.6.0
but the same settings.json can’t be found in the same directory under v3.6.1 or v3.6.2
We are using the settings.json to control the default looking feel of the vscode, so this part is broken when upgrading to the latest.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 9
- Comments: 16 (5 by maintainers)
Commits related to this issue
- Use file system for settings and fix data home path It's possible that using browser storage makes more sense with settings sync, so we might want to revisit this once/if we get settings sync working... — committed to coder/code-server by code-asher 4 years ago
- sync with upstream (#1) * plugin: Plugin modules now export a single top level identifier Makes typing much easier. Addresse's Will's last comment. * plugin.ts: Fix usage of routerPath in mount... — committed to theereechee/code-server by theereechee 3 years ago
- Delete local storage patch The main goal of this patch was to make user settings stored on disk instead of in the browser, but this stopped working some time ago. Not only that but it is causing a b... — committed to coder/code-server by code-asher 7 months ago
Will be in
v3.7.3which I’ll get out today!I have a fix in a PR so hopefully we can make a new release soon.
Thanks for your investigations, @code-asher.
I create customised Docker Images containing code-server and pre-populate
~/.local/share/code-server/User/settings.json. Using the filesystem again covers this use case, too.Keep up the great work on code-server!
v3.7.3works 👍Thank you very much!
I’m not aware of a way to do this but I think maybe what we do is patch VS Code to use the filesystem again. https://github.com/cdr/code-server/issues/2231#issuecomment-721900830
@nhooyr Great stuff! Much appreciated!
Looking forward to test
v3.7.3!I have a settings.json that I place into my container to restore my User-Settings and with 3.7.2 the problem still exist.
have to downgrade to 3.6.0
The settings.json local to code-server (~/.local/share/code-server/User/settings.json) still seem to work and can be accessed from “Open Remote Settings” inside vscode, but I believe the settings.json stored in the browser’s local storage has priority and will override anything you set there.
Any news on this? I’m using a custom path for user data directory and just read this https://github.com/cdr/code-server/issues/2231. Placing a pre-populated settings.json isn’t working.
Hello,
First of all, thank you for your work, is more than appreciated ! Do you have any news about this bug ?
I can also confirm that the problem still exists with
3.7.2.As a consequence, it’s not possible, at all, to set a custom
settings.jsonfile that “persists” and that code-server picks it. 😞awesome, thanks for letting me know, will keep an eye on the release log in the future about this change.
Thank you. @code-asher you are amazing!