ConfigSync + Devcontainers: Portable Dev Environments

VS Code devcontainers solve a real problem: every developer on the team gets the same tools, the same language versions, and the same system dependencies. No more "it works on my machine" caused by different Node versions or missing native libraries.

But devcontainers are deliberately impersonal. They define the team's environment, not yours. Inside a devcontainer, you lose your shell aliases, your Git identity, your SSH keys, and your editor customizations. The environment is reproducible but uncomfortable.

ConfigSync fills this gap. The devcontainer defines what the team needs. ConfigSync adds what you personally need on top.

The key insight is separating team configuration from personal configuration:

The devcontainer is checked into the repository and shared by the whole team. Your ConfigSync configuration is personal and encrypted. They complement each other perfectly.

Add ConfigSync to the postCreateCommand to pull your personal configs after the devcontainer is built:

The remoteEnv section forwards your local CS_TOKENenvironment variable into the container. Set this once on your host machine and every devcontainer picks it up automatically.

In a devcontainer context, you typically want a focused subset of your environment:

Skip modules that the devcontainer already handles. If the devcontainer installs project-specific tools, you do not need ConfigSync to manage those. Focus on personal configs that make the container feel like home.

For more complex setups, use a dedicated script instead of cramming everything into postCreateCommand:

The script handles the case where a team member does not use ConfigSync. They still get the full devcontainer environment; they just miss the personal customizations. No one is forced to adopt ConfigSync to contribute to the project.

Devcontainers plus ConfigSync gives you reproducibility and personalization. The team gets consistent environments. Each developer gets their own shell, identity, and preferences. When you switch projects, the devcontainer changes but your personal layer stays the same. It is the development environment you always wanted.