Skip to content

Provide support to synchronize settings across machines  #2743

Closed

Description

@SrTobi

There are quiet some extensions out there to handle setting synchronization between multiple computers. And in my opinion they are very important: Since vscode is very customizable with settings, keyboardshortcuts and extension it is very hard to synchronize those things between multiple workstations. And all those extensions are not really clean solutions, because vscode does nearly nothing to support them (for example the paths vscode uses are not exposed, see #2741).

So here some ideas to make synchronization clean and extensible:

  • add a contribution point for synchronization extensions
    • Those extensions should not have to gather all the files that have to be synced. vscode should do this and then pass them to the extensions
    • Such an extension's job is only to upload/download the files, passed to them (so we can have the gist upload/svn upload/git repo upload/dropbox/filesystem/onedrive/ftp/other services.
    • Or maybe gather all settings into one big json object and pass that.
    • Support versioning and non versioning extensions
  • add a remote_settings.json to build on top of the workspace-settings/user-settings stack.
  • allow automatic and user triggered synchronization

Ok... just some ideas 😄

Activity

  1. Tyriar commented on Feb 5, 2016

    @Tyriar
    Contributor

    Related: #679

    This is my solution for syncing keybindings and settings on Linux and Windows if you're interested. I haven't looked too deeply at doing it with extensions yet but I did file #691 some time ago to help with this.

  2. csholmq commented on Feb 9, 2016

    @csholmq

    The plugin Sync Settings for Atom uses GitHub Gist to backup/sync:

    • Settings
    • Packages
    • Keymap
    • (Styles)
    • (Init)
    • Snippets

    Atom also supports starring packages directly in Github and then easily install them using apm stars --user thedaniel --install.

  3. felixfbecker commented on Feb 21, 2016

    @felixfbecker
    Contributor

    Imo this is a pretty low priority because most of the time settings are overwritten by workspace settings that are synced with version control anyway.

  4. csholmq commented on Feb 21, 2016

    @csholmq

    Felix Becker (@felixfbecker) Extensions are however one of those things that doesn't version control. Neither is keymap.

  5. felixfbecker commented on Feb 21, 2016

    @felixfbecker
    Contributor

    Sebastian Holmqvist (@csholmq) That is a seperate issue though. For example, there could be a .vscode/extensions.json that specifies which extensions should be installed for this project, like editorconfig or a specific debug adapter, with a semver version constraint like a package.json.

  6. egamma commented on Feb 21, 2016

    @egamma
    Member

    This is not related to the original API request raised in this issue, but there is a sync extension that is using Gists. https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync

  7. csholmq commented on Feb 22, 2016

    @csholmq

    Erich Gamma (@egamma) Exactly the functionality I sought after. But as Felix Becker (@felixfbecker) mentioned, perhaps this issue is a separate one.

  8. jokeyrhyme commented on Mar 14, 2016

    @jokeyrhyme

    It might also be nice to install an extension once on one machine, and have your other machines either prompt or automatically install the same extension everywhere else.

    Atom had an online package browser with "stars", and there was a command you could run to install everything you'd starred. Still not automatic, but it was a start.

    I know others might object, but I personally have no problem having to log in to VSCode with my Microsoft account once per machine, if it facilitated this level of convenience. Maybe a synchronisation framework or something could be offered, so that provider-specific extensions could implement authentication and cloud-persistence (e.g. one for Microsoft, one for Google Drive, Dropbox, etc).

  9. golf1052 commented on Apr 6, 2016

    @golf1052
    Member

    I wrote an extension a while ago (here, also hasn't been updated in a while) that tried to help sync extensions between computers using file synchronization services. Originally I only supported syncing themes because syncing extensions seemed somewhat messy.

    I think this should be the right way to maintain extensions between computers. Keep a list of what extensions are installed where, be able to pick and choose what extensions should be installed on which computer and then only manage syncing settings for those extensions. I assume the recommended way for extensions to manage settings is through this?

  10. felixfbecker commented on Apr 6, 2016

    @felixfbecker
    Contributor
  11. ToMakeSense commented on Nov 21, 2016

    @ToMakeSense

    Very much agree with you, Add features--Account & Synchronization, handling setting synchronization and extensions synchronization(Mark extensions owned), what will make it much easier to install and to synchronize VS code between multiple computers.
    Another extensions that syncs extensions: https://marketplace.visualstudio.com/items?itemName=golf1052.code-sync

  12. 130 remaining items

  13. pycharmer1221 commented on Jul 18, 2020

    @pycharmer1221

    Elliot Labs LLC (@elliot-labs) and Brian Hauger (@haugerbr)
    thanks,
    I also don't know that gist is not private
    so now I am thinking of writing some scripts for uploading settings to the cloud
    and one script to download and install

    I have also build a program that shows me scripts on startup
    so I can put those script in there.

  14. escape0707 commented on Jul 18, 2020

    @escape0707

    Guys, vscode-insiders's sync isn't an option?

  15. jakobhviid commented on Jul 18, 2020

    @jakobhviid

    I agree with Escape0707 (@escape0707). Vs code insiders now has settings sync that will soon hit the public release. This is effectively a non problem and has been addressed.

  16. haugerbr commented on Jul 19, 2020

    @haugerbr

    Escape0707 (@escape0707) Jakob Hviid, PhD (@jakobhviid) I'm aware of it and it's exactly what I'm planning on using once it moves to the normal VSCode builds. For now I'm still using settings sync while I wait.

  17. added a commit that references this issue on Aug 13, 2020
  18. sandy081 commented on Aug 17, 2020

    @sandy081
    Member

    Settings Sync (preview) feature has landed into stable (1.48), hence closing this.

    Please create separate issues for other requests or bugs.

  19. haugerbr commented on Aug 17, 2020

    @haugerbr

    Sandeep Somavarapu (@sandy081) is having seperate profiles within the same account a feature that has been requested already? For example, if I want to use my github account for the authentication method but want seperate work/personal profiles. For now I use seperate accounts which I actually like better for personal/work separation but I can see a use case where people want multiple personal profiles. I will open up a feature request for it if it does not already exist.

  20. sandy081 commented on Aug 17, 2020

    @sandy081
    Member

    Please go through the existing settings sync issues and create a one if does not exist.

  21. haugerbr commented on Aug 17, 2020

    @haugerbr

    Found it. Tagging it here in case anyone reading this thread is also interested in tracking it #92393

  22. Chiramisudo commented on Sep 15, 2020

    @Chiramisudo

    Please join me in a nice round of applause and show of great appreciation for adding this feature (as of 1.48). I am thrilled and elated! Thank you so much VS Code team!! 👏🏼👏🏼👏🏼

    Excited Guy

    However, if you could allow me just two minor gripes:

    1. I seem to have to re-authenticate after some very short timeout (a day perhaps?) and a restart of VS Code.
    2. Authentication takes place in a browser, and since I have tabitis and sometimes don't have my browser open, this becomes somewhat... irksome.
  23. sandy081 commented on Sep 15, 2020

    @sandy081
    Member

    Thanks.

    I would suggest to open new issues for the problems you are facing with steps to repro.

  24. locked and limited conversation to collaborators on Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

configVS Code configuration, settingsplan-itemVS Code - planned item for upcomingsettings-sync

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址