Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

443
Vistas
Same VSCode-Settings for the whole crew?

We want to have the same VSCode settings for the whole crew of developers. Also it would be fine to have a oneline command to tear VSCode down and restart it from scratch with predefined settings and plugins so that you do not have to worry about trying out plugins and getting beck to the known state. Kind of Config-as-Code for VSCode.

I already found:

  • https://code.visualstudio.com/docs/editor/extension-gallery#_command-line-extension-management
  • https://github.com/microsoft/vscode-dev-containers
  • https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync&ssr=false#qna
  • https://github.com/gantsign/ansible-role-visual-studio-code-extensions
  • https://code.visualstudio.com/docs/remote/containers
  • https://github.com/gantsign/ansible-role-visual-studio-code

But non of these provides a good solution to me

We are using Mac and Windows machines and develop most of the time locally (not remotely in the cloud or the like).

I imagine like having a script like

.... projectname up

or

.... projectname reset

(or

.... projectname down)

to receive/reset the configured settings and newest plugins that have been configured for the project.

Have any ideas or use a similar solution already?

over 4 years ago · Santiago Trujillo
3 Respuestas
Responde la pregunta

0

After doing a lot of research, playing with Docker, Ansible and so on... it seems that although I excluded it at first the plugin Settings Sync Plugin from Shan Khan is the way to go. It has round about 1 million installs!

Only dependency - you need a GitHub account to host your configs. That is what held me back at first - but it should be not that much of a problem to get one for everyone in the team and connect it to like a company-github-account.

over 4 years ago · Santiago Trujillo Denunciar

0

Copy the files settings.json and keybindings.json to your target machine(s) to copy the settings. You can find those files here:

  • Win: ~\AppData\Roaming\Code\User
  • Mac: ~/Library/Application Support/Code/User/
  • Linux: ~/.config/Code/User

You can copy extentions from ~/.vscode/extensions or C:\Users\username\.vscode\extensions from linux/mac or windows respectively.

over 4 years ago · Santiago Trujillo Denunciar

0

FalcoGer's answer should explain how to copy the files in a way VS Code will pick them up. If you only need to copy the config files once, this solution would be fine.

If you need to "sync" these config files on a regular basis, I would advise to create a Git repository where all config files will be stored.

When cloning the repo to local machines, you can symlink the files to the config destinations (see FalcoGer's anwser). Then when you need to "sync", you only have to run git pull and restart VS Code to apply the changes.

For your other script-related question, you could create a CLI for this. Python would be the most friendly way to do this. You can find an example here.

over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda